Generating keys using controlled corruption in computer networks

ABSTRACT

The present invention is a platform and/or agnostic method and system operable to protect data, documents, devices, communications, and transactions. Embodiments of the present invention may be operable to authenticate users and may be operable with any client system. The method and system are operable to disburse unique portions of anonymous related information amongst multiple devices. These devices disburse unique portions of anonymous information and are utilized by the solution to protect sensitive data transmissions, and to authenticate users, data, documents, device and transactions. When used for authentication, login-related information is not stored in any portion of the solution, users and devices are anonymously authenticated. The solution also permits a user to access secured portions of the client system through a semi-autonomous process and without having to reveal the user&#39;s key.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/872,127, filed May 11, 2020, which is a continuation-in-part of U.S.patent application Ser. No. 16/436,142, filed Jun. 10, 2019, which is acontinuation of U.S. patent application Ser. No. 16/165,606, filed Oct.19, 2018, which claims benefit of and priority to U.S. ProvisionalApplication No. 62/574,285, filed Oct. 19, 2017, all the disclosures ofwhich are hereby incorporated by reference in their entirety for allpurposes.

FIELD OF INVENTION

This invention relates in general to the field of data security and moreparticularly to security of targeted communications and authenticationof a user of a network or system.

BACKGROUND OF THE INVENTION

All organizations are challenged with securing their data from potentialsecurity breaches. Only through data security can an organization ensurethat their communications are secure and that only authorized personsare granted access to their systems across multiple technologies. Thus,data security and authorized system access are two of the majorchallenges that organization must wrestle with today.

Presently there are many systems and methods that effect various typesof authentication of users of systems and networks. These various typesof authentication have differing levels of security and reliability. Thefollowing are examples of types of prior art authentication methods forsystems and networks.

U.S. Pat. No. 6,962,530 issued to IGT on Nov. 8, 2005, discloses anarchitecture and method for a gaming-specific platform that featuressecure storage and verification of game code and other data. The methodfurther provides a user with the ability to securely exchange data witha computerized wagering game system. This invention does not involvespreading out login information amongst multiple devices.

U.S. Pat. No. 9,053,306 issued to NEC Solution Innovators, Ltd. on Jun.9, 2015, discloses an authentication system operable to calculate afirst and a second hash value from the login information inputted by auser. A session will be established between a server and a terminal ifthe first and second hash values match each other. This invention doesnot involve holding back portions of the encrypted details.

U.S. Pat. No. 8,989,706 issued to Microsoft Corporation on Mar. 24,2015, discloses systems, method and/or techniques that relate toautomated secure pairing for devices, relating to parallel downloads ofcontent using devices. The tools for pairing the devices may performauthentication protocols based on addresses and on keys. This inventiondoes not involve holding back portions of the encrypted details.

U.S. Pat. No. 8,356,180 issued to Koninklijke Philips Electronics N.V.on Jan. 15, 2013, discloses a method for multi-dimensionalidentification, authentication, authorization and key distributionrelation to secure communications at a deep common security domain. Thisinvention cannot authenticate a transaction without the user revealingthe user's key to the system.

U.S. Pat. No. 6,847,995 issued to United Devices, Inc. on Aug. 25, 2000,discloses a security architecture and an associated method for providingsecure transmissions within distributed processing systems. Thisinvention does not involve multi-layer encryption or holding backportions of the encrypted details.

U.S. Patent Application Publication No. 2017/0149796 filed by YaronGvili on Nov. 23, 2016, discloses a system and technique for allowing athird party verifier to verify aspects of secured data, or thesuccessful communication thereof. This invention does not involvemulti-layer encryption or holding back portions of the encrypteddetails.

U.S. Patent Application Publication No. 2011/0246779 filed by IsamuTeranishi on Jun. 6, 2011, discloses a zero-knowledge proof system thatallows a discrete-logarithm zero-knowledge proof. This invention doesnot involve multi-layer encryption or holding back portions of theencrypted details.

The prior art encryption methods and systems are particularly vulnerableto the intervention of third parties into the transfer of data andinformation between a user and a user and a system or network. If thethird party can access data in transit, it can extrapolate login detailsfrom such information. If all of the login details are available fromdata transferred between the user and the system then the third partymay be able to login to the system using the user's login details. Thiscreates a security hazard for present day systems if knownauthentication methods and systems are utilized.

What is needed is an authentication method and system that will protecta user's login details from being obtained through third partyinterference with transmitted data.

SUMMARY OF THE INVENTION

According to some embodiments, a method of processing keys generatedusing controlled corruption may comprise registering a first computingdevice at one or more servers, the one or more servers comprising asecurity engine and an action engine; receiving, at the one or moreservers, a first privacy code and one or more parameters associated withfirst data from the first computing device, the first privacy code beingbased on first user input at the first computing device and the firstdata being based on second user input at the first computing device;generating, at the one or more servers, a chunk count and a public key,wherein the chunk count is based on the one or more parametersassociated with first data, and the public key is part of an asymmetriccryptographic key pair; transmitting the chunk count and the public keyfrom the one or more servers to the first computing device; receiving,at the one or more servers, data associated with a quantity of privacykeys and a second privacy code from the first computing device, wherein:the privacy keys are based on the first data, the chunk count, and oneor more corruptors, the second privacy code is based on the firstprivacy code, and the quantity of the privacy keys is equal to the chunkcount; generating, at the one or more servers, second data based on theprivacy keys, the generating the second data comprising steps of:concatenating the privacy keys to generate a concatenated key, andremoving the one or more corruptors from the concatenated key togenerate the second data.

According to some embodiments, a method of processing keys generatedusing controlled corruption may comprise generating, at the one or moreservers, two or more chunk names; and transmitting the two or more chunknames to the first computing device.

According to some embodiments, the privacy keys are further based on thetwo or more chunk names.

According to some embodiments, concatenating the privacy keys togenerate the concatenated key is based on the two or more chunk names.

According to some embodiments, the one or more corruptors comprisesthree corruptors.

According to some embodiments, at least one of the corruptors is basedon the first privacy code.

According to some embodiments, removing the one or more corruptors togenerate the second data comprises removing one or more first corruptorsfrom the concatenated key to generate first cleaned data; removing oneor more second corruptors from the first cleaned data to generate secondcleaned data; removing one or more third corruptors from the secondcleaned data to generate a base 64 of compressed data; decoding the baseof the compressed second data to generate the compressed data; anddecompressing the compressed data to generate the second data, whereinthe privacy code is used to remove at least one of the one or more firstcorruptors, the one or more second corruptors, and the one or more thirdcorruptors.

According to some embodiments, the first privacy code is used to removeat least one of the corruptors.

According to some embodiments, the second privacy code is used to removeat least one of the corruptors.

According to some embodiments, the first data comprises a targetedcommunication.

According to some embodiments, the second user input comprises at leastone of an alphanumeric string of characters, biometric data, a password,an eye scan, a photograph, and a fingerprint.

According to some embodiments, a method of generating keys usingcontrolled corruption may comprise the steps of: generating a firstprivacy code and one or more parameters associated with first data at afirst computing device, the first privacy code based on first user inputand the first data based on second user input; transmitting the firstprivacy code and the one or more parameters associated with the firstdata from the first computing device to one or more servers; receiving,at the first computing device, a chunk count and a public key from theone or more servers, wherein the chunk count is based on the one or moreparameters associated with the first data and the public key is part ofan asymmetric cryptographic key pair; compressing, at the firstcomputing device, the first data to generate compressed first data;generating, at the first computing device, a first pre-key based on thecompressed first data and one or more first corruptors; generating, atthe first computing device, the second pre-key based on the firstpre-key and one or more second corruptors; generating, at the firstcomputing device, two or more chunks based on the second pre-key and thechunk count; generating, at the first computing device, two or moreprivacy keys based on the two or more chunks; and transmitting the twoor more privacy keys to the one or more servers.

According to some embodiments, the generating the two or more chunksbased on the second pre-key and the chunk count comprises: corruptingthe second pre-key using a salt to generate a third pre-key; corruptingthe third pre-key using one or more third corruptors; and dividing thecorrupted third pre-key into the two or more chunks based on the chunkcount.

According to some embodiments, a method of generating keys usingcontrolled corruption may comprise receiving, at the first computingdevice, two or more chunk names.

According to some embodiments, the two or more privacy keys areadditionally based on the two or more chunk names.

According to some embodiments, a method of generating and distributingkeys using controlled corruption may comprise registering a firstcomputing device at one or more servers; receiving, at the one or moreservers, a first privacy code and one or more parameters associated withfirst data from the first computing device, the first privacy code beingbased on first user input at the first computing device and the firstdata being based on second user input at the first computing device;generating, at the one or more servers, a chunk count and a public key,wherein the chunk count is based on the one or more parametersassociated with first data, and the public key is part of an asymmetriccryptographic key pair; transmitting the chunk count and the public keyfrom the one or more servers to the first computing device; receiving,at the one or more servers, data associated with a quantity of firstprivacy keys and a second privacy code from the first computing device,wherein the first privacy keys are based on the first data, the chunkcount, and one or more corruptors; the second privacy code is based onthe first privacy code; and the quantity of the first privacy keys isequal to the chunk count; generating, at the one or more servers, seconddata based on the first privacy keys, the generating the second datacomprising the steps of: concatenating the privacy keys to generate aconcatenated key; removing the one or more corruptors from theconcatenated key to generate the second data; generating, at the one ormore servers, a result based on the second data; generating, at the oneor more servers and based on the result, a receiver identifier and aprivacy code identifier, wherein the receiver identifier is associatedwith one or more nodes and the privacy code identifier is based on thesecond privacy code; and distributing the first privacy keys, thereceiver identifier, and the privacy code identifier to the one or morenodes.

According to some embodiments, a method of generating keys usingcontrolled corruption may comprise the steps of receiving, at the one ormore servers, two or more privacy keys based on third data from thefirst computing device; and generating sign-in data, wherein the sign-indata is based on the two or more privacy keys based on the third data.

According to some embodiments, a method of generating keys usingcontrolled corruption may comprise the steps of retrieving, based on atleast one of the receiver identifier and the privacy code identifier,the privacy keys stored at the one or more nodes; and generatingenrollment data, wherein the enrollment data is based on the privacykeys retrieved from the one or more nodes.

According to some embodiments, a method of generating keys usingcontrolled corruption may comprise the steps of comparing the sign-indata to the enrollment data; and generating a result.

According to some embodiments, a system may comprise a server, theserver comprising: a memory comprising server instructions; and aprocessing device configured for executing the server instructions,wherein the server instructions cause the processing device to performoperations of: registering a first computing device at one or moreservers, the one or more servers comprising a security engine, an actionengine, a library, and one or more nodes associated with the one or moreservers; receiving, at the one or more servers, a first privacy code andone or more parameters associated with first data from the firstcomputing device, the first privacy code being based on first user inputat the first computing device and the first data being based on seconduser input at the first computing device; generating, at the one or moreservers, a chunk count and a public key, wherein the chunk count isbased on the one or more parameters associated with first data, and thepublic key is part of an asymmetric cryptographic key pair; transmittingthe chunk count and the public key from the one or more servers to thefirst computing device; receiving, at the one or more servers, aquantity of privacy keys and a second privacy code from the firstcomputing device, wherein: the privacy keys are based on the first data,the chunk count, and one or more corruptors; the second privacy code isbased on the first privacy code; and a number of the privacy keys isequal to the chunk count; generating, at the one or more servers, seconddata based on the privacy keys, the generating the second datacomprising the steps of: concatenating the privacy keys to generate aconcatenated key; and removing the one or more corruptors from theconcatenated key to generate the second data.

In this respect, before explaining at least one embodiment of theinvention in detail, it is to be understood that the invention is notlimited in its application to the details of construction and to thearrangements of the components set forth in the following description orillustrated in the drawings. The invention is capable of otherembodiments and of being practiced and carried out in various ways.Also, it is to be understood that the phraseology and terminologyemployed herein are for the purpose of description and should not beregarded as limiting.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention will be better understood and objects of the inventionwill become apparent when consideration is given to the followingdetailed description thereof. Such description makes reference to theannexed drawings wherein:

FIG. 1 is a system drawing showing an embodiment of the authenticationsystem of the present invention.

FIG. 2 is a system drawing showing a configuration of elements operableto undertake a transfer of data between the client system and theverification system of an embodiment of the present invention.

FIG. 3 is a system drawing showing a configuration of elements operableto undertake a registration process of an embodiment of the presentinvention.

FIG. 4 is a system drawing showing a configuration of elements operableto undertake an access process of an embodiment of the presentinvention.

FIG. 5 is a system drawing showing a synchronization element operable toprocess a hashed OY-packet portion in accordance with an embodiment ofthe present invention.

FIG. 6 is a system drawing showing a configuration of elements operableto undertake a decoding process of an embodiment of the presentinvention.

FIG. 7 is a system drawing showing elements of a user device of anembodiment of the present invention.

FIG. 8 is a system drawing showing elements of a client system of anembodiment of the present invention.

FIG. 9 is a system drawing showing elements of a client display unit ofan embodiment of the present invention.

FIG. 10 is a system drawing showing elements of an verification systemof an embodiment of the present invention.

FIG. 11 is a system drawing showing a configuration of elements operableto undertake processing of a user authentication request to access thesecure portion(s) of a client system in accordance with an embodiment ofthe present invention.

FIG. 12 is a system drawing showing a configuration of elements operableto undertake the generation and processing of noise and keys forauthentication of a user in accordance with an embodiment of the presentinvention.

FIG. 13 is a system drawing showing a configuration of elements operableto undertake the verification of keys for authentication of a user inaccordance with an embodiment of the present invention.

FIG. 14 is a system drawing showing a configuration of elements operableto undertake the verification of tokens for authentication of a user inaccordance with an embodiment of the present invention.

FIG. 15 is a system drawing showing a configuration of elements operableto undertake the verification of a challenge via a client display systemfor authentication of a user in accordance with an embodiment of thepresent invention.

FIG. 16 is a system drawing showing a configuration of elements operableto undertake the verification of a challenge via a user device forauthentication of a user in accordance with an embodiment of the presentinvention.

FIG. 17 illustrates a registration method, according to one embodimentof the present invention.

FIG. 18 illustrates a method of creating one or more keys, according toone embodiment of the present invention.

FIG. 19 illustrates a method of distributing one or more keys, accordingto one embodiment of the present invention.

FIG. 20 illustrates a login method, according to one embodiment of thepresent invention.

FIG. 21 illustrates a method of creating one or more keys, according toone embodiment of the present invention.

FIG. 22 illustrates a method of distributing one or more verificationkeys, according to one embodiment of the present invention.

FIG. 23 illustrates a method of verifying a verification key in a localdatabase, according to one embodiment of the present invention.

FIG. 24 illustrates a method of validating a verification process,according to one embodiment of the present invention.

FIG. 25 illustrates a method of generating one or more bar codes,according to one embodiment of the present invention.

FIG. 26 illustrates a method of generating one or more keys, accordingto one embodiment of the present invention.

FIG. 27 illustrates a method of generating one or more keys, accordingto one embodiment of the present invention.

FIG. 28 illustrates a method of generating one or more keys, accordingto one embodiment of the present invention.

FIG. 29 illustrates a method of establishing a web session, according toone embodiment of the present invention.

FIG. 30 illustrates a system for generating keys using controlledcorruption, according to some embodiments.

FIG. 31 illustrates a method of generating keys using controlledcorruption, according to some embodiments.

FIG. 32 illustrates a method of generating keys using controlledcorruption, according to some embodiments.

FIG. 33 illustrates a method of generating keys using controlledcorruption, according to some embodiments.

FIG. 34 illustrates a method of generating keys using controlledcorruption, according to some embodiments.

FIG. 35 illustrates a method of using keys generated using controlledcorruption for authentication, according to some embodiments.

In the drawings, embodiments of the invention are illustrated by way ofexample. It is to be expressly understood that the description anddrawings are only for the purpose of illustration and as an aid tounderstanding, and are not intended as a definition of the limits of theinvention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

The present invention is an authentication method and system operable toauthenticate users, data, documents, devices and transactions.Embodiments of the present invention may be operable with any system ornetwork of any organization or individual. The authentication method andsystem are operable to disburse unique portions of login relatedinformation amongst multiple devices. The disbursed portions of loginrelated information are utilized by the system to authenticate users,data, documents, devices and transactions without revealing the loginrelated information to the system. The login related information isencrypted and/or hashed through multi-layer encryption and/or hashing,and some of the encrypted and/or hashed details are held back. Thedevices wherein login related information is stored will all be utilizedin the authentication method and system. Login related informationprovided to a user is not revealed to and/or stored in the system or anyuser device. The authentication of data, documents, devices andtransactions does not require a key to be revealed to the system.

Any reference herein to “client system” means either the network orsystem of an organization or individual. Any reference herein to a “userdevice” means a device utilized by a user to login to the client system,such as a laptop, a tablet, a cell phone, a smart phone, a desktopcomputer, smart watch, a computing device, whereby a user can login tothe client system or any other device which requires a secure login. Anyreference to the “transfer of information” between a user and the clientsystem can include any creation, transfer or storage of informationoccurring in relation to the system.

For clarity, when reference is made to any unit or element of theauthentication system “accessing” another unit or element, this mayinvolve any of the following: (i) the unit or element accessing theother unit or element to obtain information therefrom; or (ii) the unitor element sending a request to the other unit or element forinformation to be retrieved or generated, and once such information isretrieved or generated in response to the request, such information canbe sent to the unit or element that sent the request.

When a user logs into a client system using a user device, the creation,transfer, storage or authentication of login related information betweenthe user device and the client system can be vulnerable to attack by athird party. As a result of the third party's attack on user device orclient system, during the creation, transfer, storage and/orauthentication of login related information between, the third party mayobtain and/or use such information for nefarious purposes. For example,the third party may login to the client system using the login detailsthey have obtained and thereby achieve unauthorized access to the clientsystem or move laterally to systems connected to the client system byobtaining more login related information from the client system orotherwise. As another example, the third party may utilize the data,documents or transaction information obtained due to the attack for avariety of unauthorized purposes (i.e., dissemination of the informationto other parties, use of the information to obtain a market advantage,holding the information hostage for a ransom, espionage, subversionetc.). The present invention decreases the vulnerability of a clientsystem to such unauthorized usage of the client system or data,documents or transaction information created, transferred and/or storedbetween such client system and a user device.

The method of the present invention involves a user utilizing a userdevice to login to the client system of an organization or person. Thelogin related information will be hashed and/or encrypted through asingle or multi-layer hashing and/or encryption process(es). Inparticular at least a portion of the encrypted and/or hashed key may begenerated and stored in the user's device. Other unique portions of thelogin related information will be stored in other devices in theenvironment. The disbursement of unique portions of the login relatedinformation amongst multiple devices means a third party who accessesinformation transferring between the client system and the user's devicewill not be able to obtain any or all of the information required for asuccessful login to the client system.

Moreover, in one aspect of the current system, to authenticate datadocuments, devices, transactions and/or a user, the user's device willneed to prove to the client system that it has valid keys and/or thatthe device has been previously authenticated This will be achieved bythe present invention without the user device having to reveal a key orkeys to the client system. Thus, the authentication of data, documents,devices, transaction and users can occur without the user having toreveal his or her key to the client system.

The login related information will be created uniquely and will not bestored and/or transmitted; this along with the user device assistedmultipoint authentication prevents unauthorized third party access tothe client system.

As most prior art authentication systems involve the creating, storing,transfer and single point authentication of login related informationbetween a user's device and a client system, the prior art systems arevulnerable to such information being compromised by third parties. Oncesuch information is obtained by a third party, the information can beused to login at a single authentication point to the system networkwithout authorization, or unauthorized use of the data, documents ortransaction information. The present invention offers a benefit over theprior art systems in that it is not vulnerable to such third partyaccess to information that would allow unauthorized access to a clientsystem, or to data, documents or transaction information. Theauthentication system of the present invention addresses the problem ofprior art authentications that can be compromised at creation, storage,transit and authentication point.

As an example of another benefit of the present invention over the priorart system is that prior art systems are not generally operable with anytype of client system, or with any type of user device. The presentinvention provides an organization with a secure authentication systemthat will provide the necessary secure access to a user to access theorganizations' data across any platform, solution or environment. Thepresent invention can be implemented by any organization for use withany type of client system, and with any user device on any platform.

Yet another example of a benefit of the present invention over the priorart is that the present invention is operable to undertake hiveauthorization of devices within an environment. For example, multiplemobile and/or storage devices across geo-temporal zones can beauthorized in the course of hive authorization. Prior art systems arenot operable to undertake hive authorization across geo-temporal zones.

Embodiments of the present invention may incorporate multiple componentsoperable to authenticate a user for the purpose of a user login to aclient system having secure portions therein, or for the purpose of theuser accessing the secure portions of such system. For example, oneembodiment of the present invention may incorporate three maincomponents as follows: (1) Synchronized Multi-Faceted Authentication(SMFA); (2) Interactive Semi-Manual Authentication (ISMA); (3)Transaction Authentication. To provide an example of such an embodimentof the present invention these three components of an embodiment of thepresent invention all described below. A skilled reader will recognizethat other configurations of the present invention are possible,including configurations that only include one or two of the threecomponents described below, or configurations that incorporate othercomponents.

Synchronized Multi-Faceted Authentication (SMFA)

The authentication process for a user of the present inventionauthentication method and system operates so that the encrypted and orhashed portions of random multi-unit login related information aredisbursed amongst devices (e.g., user and/or system devices and storageunits) and all of such or more of such devices must be utilized toauthenticate the user.

Therefore, if login data is compromised at creation, transit, storage orat authentication, such as by unauthorized access by a third party, onlyan encrypted and or hashed partial portion of the time sensitive randomlogin related information of the unknown user(s) will be obtained thisdata will be unusable to authenticate the user.

More specifically, the present invention is operable to require a userto engage in a challenge, such as, a static challenge that may be a pinand/or pattern challenge, an animated and/or non-animated challenge, agraphical and/or non-graphical challenge, a two dimensional and/or threedimensional challenge, a moving and/or static gamified challenge, and/ora non-gamified interface challenge, in order to login to the clientsystem. The system may choose a series of units and may use these togenerate a challenge. Each unit is randomly assigned multiple digits.that may change at each login event. A user may select multiplechallenges in the same authentication event and in any subsequentauthentication events.

The series of units chosen during the challenge are divided by theauthentication system into multiple unique system portions. The units ineach unit portion may be hashed or encrypted individually to generateunit results, and then the units in each system portion are hashedand/or encrypted collectively to generate system portion results. Thenumber of hashes and/or encryptions applied to each unit in a systemportion and to each system portion can vary.

Portions of the hashed and/or encrypted results are stored in differentdevices of the distributed architecture of the client or other systemand a portion is stored in the user's device. For example, portions ofthe hashed and/or encrypted results may be stored in multiple user andsystem devices.

All of the client system devices containing hashed and/or encryptedpartial data, as well as the user device, must validate themselves. Oncedevices are authenticated they might then co-authenticate the user.

The present authentication system invention is platform agnostic, so itcan be used with any client system.

Interactive Semi-Manual Authentication (ISMA)

The authentication process for a user of the present invention operatesso that the login information is encrypted and/or hashed usingmulti-layer encryption and/or hashing functions. The portions of randomencryption and/or hashing details that are held back and manuallytransmitted and are not stored in the client system, or in the userdevice, thereby decreasing the possibility of compromise duringtransmission, storage or authentication.

The system of the present invention provides a key (i.e., key #1) to themobile device. All keys in the present invention are encrypted and/orhashed using multi-layer encryption and/or hashing functions.

The encrypted key is required to be used in the authentication processof the present invention, and therefore the user must first authenticateusing the SMFA process described herein, and thereby validate the keyand authenticate the user's device.

The system will generate a challenge based on random encrypted keys thatwill change at each login event. The authenticated user will use theirauthenticated device to scan the challenge. At the end of this processpart or whole portions of the random encrypted key will be sent to theuser device.

In some embodiments of the present invention there may be another set ofencrypted random keys that may be generated by the user device that willalso change at each login event. Multiple keys that can be combined toform an encrypted shared secret key; portions of or the entire encryptedshared secret key will be sent to the client system of the organizationthat is requesting authentication of the user.

Multiple layers of encryption may be generated by the user device. Suchencryption may be applied to elements individually or collectively. Forexample, random three or more digits (that may change during each loginevent) along with salt and iv can be generated by the user device, orother types of encryption and/or hashing may be applied. Another layerof encryption may be added collectively to the prior encryption.

Multiple random characters will be removed from the package that resultsfrom the multiple layers of encryption. For example, six randomcharacters may be removed from the package. The multiple random digitsand characters will be provided to the user and the encrypted detailsare sent to the client system requesting authentication of the userdevice.

The client system requesting authentication of the user device willchallenge the user to provide the information given to the user device.Only upon the user providing such information will the client system beable to authenticate the user. This process reduces the possibility of athird party intercepting, guessing or knowing the user's logininformation.

When the user is authenticated the session will be authenticated throughtime and geo-based access code. For example, the geo-based access codemay be a token or any other type of geo-based access code. The geo-basedaccess code may be invalidated if the time expires or the geo aspect isinvalidated. For example, the geo aspect may be invalidated if the useris not located within the geo-location relating to the geo-based accesscode.

Transaction Authentication

The authentication process for a user of the present inventionauthentication system operates so that the transactions areauthenticated without the user having to reveal his or her key to theclient system. The client system does not know the user key or if theuser has a key. The user device has to prove to the system that it hasvalid keys and that the user and device have been authenticated, withoutrevealing the key to the system. In order to achieve this the userdevice will have to authenticate using the SMFA process described hereinand/or the ISMA process described herein. Once the user device isauthenticated, the user device may use a random temporary key it has orthat it has received.

The system will generate a security challenge. This challenge may besecured using features, such as, multi-layer encryption, digitalsignature and or hashing. The secured package is sent to the user devicerequesting authentication. The user device will verify the package andmay use the decryption key provided to the display or solve thechallenge.

As an example, one embodiment of the present invention may be operablesuch that the system will generate multiple random digit alpha numericcodes with one or more digits being blank, the corresponding alphabet ornumeral to be filled-in to the blank will be also sent to the user withthe challenge in the ISMA process. For example, the system may generatesix or more multiple random digit alpha numeric codes, or any othernumber of random digit alpha numeric codes.

The system will generate and encrypt the six or more random digitalphanumeric code as well as other elements. For example, the system mayencrypt the six or more random digit alphanumeric code, Additionalencryption and security features (which may include but not limited tosalt, iv, secure keys etc.) may also be applied by the client system.The system will then add a digital signature to the results of theencryptions. This encrypted & signed package is then sent to the userdevice requesting to be authenticated.

The user device will verify the digital signature and then use thedecryption key provided to recreate the six or more digit alpha numericcode along with corresponding alphabets or numerals.

The user device then encrypts the recreated information. along with thesecurity features. The user device will then add a digital signature tothe results of the encryption. This encrypted and signed package is thensent to the client system engaged in the authentication process.

The client system receives the message from the user device, and uponreceipt will verify the digital signature, decrypt the message andcompares the message with the sent message. If the comparison shows thatthe received message is the same as the sent message then the clientsystem knows that the user has the required key When the user device isauthenticated the session will be authenticated through time andgeo-based access codes, these access codes will be invalidated if thetime expires or the geo is invalidated, as previously discussed herein.

A skilled reader will recognize that the method and system forauthentication of the present invention may be implemented in a varietyof manners. FIGS. 1-17 provide some examples of embodiments of thepresent invention, and these are described herein.

As shown in FIG. 1, the authentication system incorporates many elementsincluding a client system, a user system, a verification system, andmultiple storage units. The authentication system is operable to achievemany functions including proving and verifying a user's login.

The user system 102 is used by the user to login to the client system902. The user system is operable to engage in verifying the user'sidentity as well as other activities, as described herein. The user'sidentity must be verified by the client system in order for the user togain access to the secured area of the client system. The verificationsystem 202 is operable to engage in verifying the identity of the userto the client system.

When the user, through the user device 90, wants to access a securedarea of the client system, the user will have to first prove the user'sidentity to the client system. Once the client system receivesverification of the identity of the user, the system can then permit theuser to access the secure contents of the client system.

The user uses the user system to prove its identity and to gain accessto the secured area of the client system. The verification system 202 isoperable to verify the authenticity of the user's identity. Thesynchronization system 300 is a collection of one or moresynchronization elements 302A . . . 302N, operable to function in asynchronized manner to approve the authenticity of user's identity.

The user system may incorporate multiple elements. In one embodiment ofthe present invention the user system may incorporate a proving unit104, a display unit 106, a processing unit 108, an approval unit 112, astorage unit 110 and a communications unit 114. The proving unit isoperable to prove the initial identity of the user system 102 to theverification system. The display unit is operable to display informationto a user, for example, such as a challenge or any other informationtransferred from the client system, the verification system or any othersystem or element of the present invention to the user system. Thedisplay unit is further operable to display information generated by theclient system to the user. The display unit may further be connected toan input unit, or have a touch screen or other input operability,whereby a user can input information. The information inputted by theuser may be displayed on the display unit, or may otherwise be collectedby the user system and stored, transferred to the client system oranother system or element of the authentication system, or processed bythe user system. The processing unit 108 will be responsible for all theprocessing capacity within the system. The approval unit 112 will beresponsible for accessing the challenge and response and providing aresult and the storage unit will be responsible for storing bothtemporary and permanent data. The communication unit 114 is responsiblefor all external communications.

The verification system 202 may incorporate multiple elements. In oneembodiment of the present invention the verification system mayincorporate a masker unit 204, a N-packet generator 206, a reportgenerator 208, a processing unit 210, an approval unit 212, one or morestorage units 214A . . . 214N, and communications unit 216. The maskerunit is operable to generate one or more unique non-identifyingidentifiers for the client system and the user system. The processingunit 210 is operable to processing of information and data as requiredby the authentication system. The approval unit 212 is operable toaccess the responses received internally in the system and providing aresult that can be sent to the processing unit or sent to a receiverthat is external to the system via a communication unit. The one or morestorage units are operable to store both temporary and permanent data.The N-packet generator 206 is operable to generate packets ofauthentication information. The communication unit 216 is operable toreceive and transfer all communications with all elements of theauthentication system that are external to the verification system(i.e., the client system, the user system, etc.).

A skilled reader will recognize that in embodiments of the presentinvention some or all of the units described as elements of theverification system in FIG. 1 may be incorporated within other systemsor elements of the authentication system, such as the client system. Insome embodiments of the present invention some or all of the unitsdescribed as elements of the verification system in FIG. 1 may bestandalone elements that are not incorporated in any system of theauthentication system, but are generally incorporated in theauthentication system.

The synchronization system 300 may incorporate one or moresynchronization elements 302A . . . 302N, and each synchronizationelement may incorporate multiple units. In one embodiment of the presentinvention at least two synchronization elements may incorporate aproving unit 304A . . . 304N, a storage unit 308A . . . 308N, aprocessing unit 306A . . . 306N, an approval unit 312A . . . 312N, and acommunications unit 310A . . . 310N. The proving unit 304A is operableto prove the initial identity of the synchronization system 300 to theverification system 202.

Communication between the user system, the verification system and thesynchronization elements is received by and transferred from thecommunication unit of such system and/or elements. All suchcommunication between the systems and/or elements may be secured by theuse of one or more masking functions, the one or more masking functionsmay include, hashing and/or encryption.

As shown in FIG. 2, data may be transferred between the client system902 and a masker unit 204 of the verification system via thecommunication unit 216 of the verification system. During the initialcommunication between the client system and the verification systemrelating to the set-up of a new user who wants to use the client system,the client system may communicate with the masker unit of theverification system to request credentials required for the new user toestablish a secure connection with the client system. The masker unitgenerates unique secured credentials the client system can use toestablish a link between the client system and the verification system.These unique credentials may include for example a client ID, or otherforms of credentials.

When the trusted connection is established between the client system andthe verification system, the masker unit performs a process, such as, acalculation, an algorithm or another type of process that will generatea unique non-identifying identifier that is a secret for the user. Theunique non-identifying identifier may be stored in one of the storageunits 214A (or any of storage units 214A . . . 214N) incorporated in theverification system.

The masker unit may use a masking function such as hashing, encryption,and or some other masking function to render the non-identifyingidentifier secure. The client system may also provide the verificationsystem with a list of all available synchronization elements. Inembodiments of the present invention, one or more of the synchronizationelements may be stored in one or more of the storage units 214A . . .214N of the verification system.

As shown in FIG. 3, the registration process of the present inventionmay involve the operation of elements of the authentication system asrequired during the initial interaction of the user with theauthentication system, in order for the user to register with the clientsystem. All communications between the client system, elements of theuser system, elements of the verification system and elements of thesynchronization system are via the communication units of the usersystem, the verification system and the synchronization system, as shownin FIG. 3. The user must register with the client system to beauthorized to access the secure portions of the client system. Duringthe initial registration the proving unit 104 accesses one or morestorage units 110 of the client system to retrieve proving information.The proving information may include a non-identifying identifiergenerated by the masker unit, a secret that has also been generated bythe masker unit, and may also include information that may identify theuser device, a unique application number, and or other informationrelating to the user, for example biometric information (e.g., theuser's fingerprint, the user's retina scan, or other biometricinformation of the user), usage information etc. Once the proving unitobtains all of the proving information, the proving information may bestored in one or more of the storage units of the user system.

The proving information that has been obtained by the proving unit 104is securely sent via the communication unit 114 of the user system tothe processing unit 210 of the verification system. The processing unit210 retrieves information for the user, via the communications unit 216of the verification system, from one or more of the storage units 214A .. . 214N of the verification system. The processing unit 210 combinesthe information it receives from the client system with the informationit retrieves from the one or more storage units of the verificationsystem to create a package of information. The processing unit sendssuch package of information to the approval unit 212.

The approval unit 212 compares the values of the package of informationit receives from the processing unit with information stored in the oneor more storage units 214A . . . 214N of the verification system, thatwas previously received from the client system. If the comparison issuccessful the approval unit will accept the connection with the usersystem. If the comparison is not successful the approval unit 212 willdeny the connection with the user system. The results of the approvalsystem are sent to the N-packet generator 206.

If the connection with the user system is not approved, the operation ofthe authentication system to attempt to register the user will end. Inone embodiment of the current invention, if the connection with the usersystem is approved, then the N-packet generator will generate a randomchallenge. The random challenge may include multiple packets(N-packets). Each N-packet contains multiple random numeric oralphanumeric/other characters (N-RANC).

The N-packets are securely sent to the display unit 106 of the usersystem. Embodiments of the present invention may apply multi-layer ofprotection, including, but not limited to encryption, hashing and/ordigital signature to provide security to the N-packets in transitbetween the N-packet generator and the display unit, for example, themulti-layer protection of both the N-RNAC and the N-packets prior totransit. In other embodiment of the present invention N packets could begenerated by an element of the user system or a different system with orwithout N-RNAC. The user interacts with this element to generate an OYpacket.

The display unit 106 receives the N-packets and displays the informationincorporated in the N-packets to the user. From the N-packets displayedthe user enters one or more N-packets, and thereby selects the N-RANCassociated with the chosen N-packets. For ease of reference theN-packets chosen by the user are the Y-packets herein. The order inwhich the Y-packets are chosen by the user is retained to become OrderedY-packet (OY-Packet) The OY-Packets are sent by the display unit 106 tothe processing unit 108 of the user system. The processing unit of theuser system splits the OY-Packet into two or more portions. Each portionmay contain two or more N-Packets.

The processing unit of the user system may mask the OY-Packetinformation by applying a masking function to each portion of theOY-Packet. For example, the processing unit of the user system may applymasking to one or more of the following: each of N-RNAC incorporated inthe OY-Packet and/or to each Y-Packet incorporated in the OY-Packetand/or to each OY-Packet. The results of one or more masking may bestored in one or more of the storage units 110 of the user system. Theresults that are not stored are sent to the processing unit of theverification system.

The challenge generated by the N-packet generator that is sent to thedisplay unit of the user system may incorporate multiple N-packets andeach N-packet may incorporate three or more N-RANG. The user may selectmultiple Y-packets that form the OY-packet. The OY-packet may be splitinto 2 portions (i.e., an OYA-portion and an OYB-portion).

The processing unit of the verification system may apply hashing and/orencryption and then select two or more random synchronization elementsof the synchronization system from a list stored in the one or morestorage units of the verification system. The selected randomsynchronization elements form a sync registry. The processing unit ofthe verification system may add a secret to the OY-packet portions,individually or collectively, and may perform a multi-layer hashingand/or encryption function on the OY-packet portions, individuallyand/or collectively. The hashed and/or encrypted unique OY-packetportions may then be distributed among one or more synchronizationelements, and be stored in one or more of the storage units in one ormore of the synchronization elements to which the OY-packet portion isdistributed. The result is that the unique OY-packet portions are storedin different synchronization elements. The distribution informationportions may be stored in a sync registry of the synchronizationelements.

As shown in FIG. 4, the authentication system may be operable to performan access process, whereby the registered user tries to authenticateitself through the operation of the verification system, in order forthe user to gain access to secure portions of the client system. Allcommunications between elements of the user system, elements of theverification system and elements of the synchronization system are viathe communication units of the user system, the verification system andthe synchronization elements of the synchronization elements of thesynchronization system, as shown in FIG. 4. The proving unit 104 of theuser system accesses one or more of the storage units 110 of the usersystem to retrieve proving information. The proving information mayinclude a non-identifying identifier and a secret.

Some or all of the proving information that has been obtained by theproving unit is securely sent via the communication unit 114 of the usersystem to the processing unit 210 of the verification system, via thecommunication unit 216 of the verification system. The processing unit210 retrieves information for the user from one or more of the storageunits 214A . . . 214N of the verification system. The processing unit210 combines information received from the client system with theinformation retrieved from one or more storage units of the verificationsystem to create a package of information. The processing unit sendsthis package of information to the approval unit 212 of the verificationsystem.

The approval unit 212 compares the values of the package of informationit receives from the processing unit 210 with information stored in theverification system that was previously received from the client system.If the comparison is successful (i.e., the comparison results in a matchbetween the compared information) the approval unit will accept theconnection with the user system. If the comparison is not successful theapproval unit will deny the connection with the user system. The resultsof the approval system are sent to the N-packet generator 206.

If the connection with the user system is not approved, the operation ofthe authentication system to attempt to register the user will end. Ifthe connection with the user system is approved, the N-packet generatorwill generate a random challenge. The random challenge may include twoor more packets (N-packets). Each N-packet contains two more randomnumbers or alphanumeric characters (N-RANC). A multi-layer hashingand/or encryption may be applied to the challenge sent to the displayunit. The hashing and/or encryption is applied by the random numbergenerator

The N-packets are securely sent to the display unit 106 of the usersystem. Embodiments of the present invention may apply multi-layerhashing and/or encryption to provide security to the N-packets intransit between the N-packet generator and the display unit. Forexample, the multi-layer hashing and/or encryption may incorporatehashing and/or encrypting the N-RNAC and/or the N-packets prior totransit. The display unit 106 receives the N-packets and displays thecorresponding information to the user. From corresponding informationdisplayed the user selects two or more corresponding information andthere by selecting N-packets, and N-RANC associated with the chosenN-packets. For ease of reference the N-packets chosen by the user arethe Y-packets herein these Y packets are ordered and are called OYPackets.

In another embodiment of the present invention, the N-packet generatormaybe present in the user system and or other systems which may generateY and/or OY packets by interaction with a user through any element fromthe user system or other systems, such as, cameras, scanners, etc.

The OY-Packets are sent by the display unit 106 to the processing unit108 of the user system. The processing unit of the user system splitsthe OY-Packet into multiple portions. Each portion contains multipleN-Packets.

The processing unit 108 of the user system retrieves previously storedOY-packet portions from one or more storage units of the user systemwhere such previously stored OY-packet portions are stored. Theprocessing unit sends the previously stored OY-packet portions and morerecently created OY-packet portions to the approval unit 110 of the usersystem. The approval unit of the user system compares the information itreceives from the processing unit of the user system with the previouslystored OY-packet portion and generates either an approval result or adenial result. The result generated by the approval unit of the usersystem (that is either an approval result or a denial result) istransferred to the processing unit of the user system. If the resultfrom the approval unit of the user system is a denial result theauthentication process is halted.

If the result of the approval unit of the user system is an approvalresult, the processing unit of the user system may store one or more ofthe OY-packet portions recently generated in one or more storage unitsof the user system, and will send the rest of the OY-packet portions tothe processing unit of the verification system. The processing unit ofthe verification system retrieves the synchronization system informationfor the user from the sync registry. The processing unit of theverification system may add a secret to the OY-packet portions itreceives and perform a multi-layer hashing and/or encryption function onthese OY-packet portions. After hashing and/or encryption the processingunit of the verification system may send the hashed and/or encryptedunique OY-packet portions to one or more of the processing units 302A .. . 320N of the synchronization elements of the synchronization system.Each processing unit of a synchronization element that receives a hashedand/or encrypted unique OY-packet portion from the processing unit 210of the verification system. Each synchronization element of thesynchronization unit that receives a hashed and/or encrypted OY-packetportion may undertake a process, as shown in FIG. 5. The processing unit306A . . . 306N of the synchronization element may decode the hashand/or encryption to determine and identify one or more N-Packets andN-RANCs. The processing unit of the synchronization element may send theN-packets and N-RANCs to the approval unit 312A . . . 312N of the samesynchronization element.

The proving unit 304A . . . 304N of the synchronization unit retrievesthe previously stored hashed and/or encrypted OY-packet portions fromthe storage unit 308A . . . 308N of the synchronization element. Theproving unit of the synchronization unit may decode the hash and/orencryption to determine and identify one or more N-packets and N-RANCsand these are sent to the approval unit of the synchronization element.The approval unit of the synchronization element compares the N-packetsand N-RANCs it received that were recently generated to those that werepreviously stored. Based upon this comparison either a pass value or afail value is generated. The generated pass value or fail value istransferred to the proving unit of the synchronization element.

The proving unit of the synchronization unit retrieves provinginformation from one or more of the storage units of the synchronizationunit and both the proving information and the pass value or fail valuethat the proving unit has received may be hashed and/or encrypted andsent to the processing unit of the verification system.

The processing unit of the verification system receives the hashedand/or encrypted results and proving information from each of theproving units of each of the synchronization elements that generatedsuch information. For clarity, multiple synchronization elements mayhave received unique OY-packet portions and each such synchronizationelement will have processed the OY-packet portions in accordance withthe method discussed herein. All communications between elements of theuser system, verification system and the client system are via thecommunication units of the user system, client system and theverification system, as shown in FIG. 6. Also as shown in FIG. 6, theprocessing unit 210 of the verification system 202 will decode theproving information it received from each synchronization element 302A .. . 302N and send the decoded information to the approval unit 212 ofthe verification system. The processing unit 210 of the verificationsystem retrieves proving information from one or more of the storageunits 214A . . . 214N of the verification system. The processing unit ofthe verification system sends the retrieved proving information to theapproval unit of the verification system. The approval unit of theverification system utilizes the information it receives to approve thesynchronization elements.

The processing unit of the verification system decodes each of the passand/or fail values it receives from the synchronization elements. Thedecoded values are saved in one or more of the storage units of theverification system as verification results. A verification resultsreport may be generated by the processing unit of the verificationsystem or a report generator 208, and this report may contain a varietyof information, for example the total synchronization elementsrequested, the number of pass values received, the number of fail valuesreceived, synchronization system trust scores and other information.

The processing unit of the verification system may hash or encrypt theverification results and send the hashed and/or encrypted verificationresult to the processing unit 108 of the user system 102, via thecommunication unit 216 of the verification system. The processing unitof the user system sends the hashed or encrypted verification result tothe client system 902. The client system submits a request forauthentication to the processing unit 210 of the verification system,via the communication unit 216 of the verification system, based uponthe verification results the client system receives. The processing unitof the verification system retrieves the verification results saved inone or more of the storage units of the verification system and sendsthe retrieved results to the approval unit of the verification system.The approval unit of the verification system reviews the retrievedresults and may approve these and send the verification results to theclient system which will then decide whether or not to authenticate theuser based on the verification report results.

After a user is authenticated and is granted access to the secureportions of the client system, the user may access information (i.e.,data, documents, transaction information, etc.) and/or provide userinformation (i.e., text, data, etc.) to the client system. As anexample, the user may access the client system to send messages, toundertake purchases that involve credit card payments, to attach ane-signature to a document, or for a variety of other purposes. In thecourse of the interaction of the user with the client system, via theuser system, user information will be transmitted between the clientsystem and the user system. The present invention is operable to protectthe security of such user and authentication related information duringcreation, transit, storage and authentication.

To achieve such security an embodiment of the present invention mayincorporate a user system, a client system, a client display unit and averification system. The user system may be incorporated wholly orpartially in the client device utilized by the user to communicate withand access the client system. A skilled reader will recognize thatembodiments of the present invention that achieve security for user andauthentication related information in transit between the user deviceand the client system may incorporate other elements.

The user will use the user device to verify the user system and theuser's credentials to the client systems. A user's credentials and theuser system must be verified in order to verify that the user isauthorized to access the secure portions of the client system. The userwill only be able to perform certain functions or access certaininformation through the secure portions of the client system if the useris authenticated. As an example, the user will only be able to approvecertain transactions through the client system if the user and the usersystem are authenticated. The client system is the system that the useris trying to gain access to and therefore requires the authentication tobe performed. The verification system of the present invention willverify the identity of the user and the user system and cause the clientsystem to recognize the user and the user system as authenticated, as isdescribed herein.

As shown in FIG. 7, a user system 101 utilized to transmit userinformation to and from the client system may incorporate multipleelements. For example, an embodiment of the present invention mayinclude a user system that incorporates an interaction unit 103, averifier generator 105, a noise generator 107, a processing unit 109, astorage unit 111, and a reader unit 113.

As shown in FIG. 8, the client system 130 of an embodiment of thepresent invention may incorporate multiple elements. For example, anembodiment of the present invention may include a client system thatincorporates a CSAP generator 131, a storage unit 133, a processing unit135, a challenge generator 137, and an approval unit 139.

As shown in FIG. 9, the client display unit 150 of an embodiment of thepresent invention may incorporate multiple elements. For example, anembodiment of the present invention may include a client display unitthat incorporates an interaction unit 151, a processing unit 153, atemporary storage unit 155 and a key generator 157.

As shown in FIG. 10, the verification system 140 of an embodiment of thepresent invention may incorporate multiple elements. For example, anembodiment of the present invention may include a verification systemthat incorporates a random key generator 141, a random text generator143, a USID generator 145 and a processing unit 147.

When the user wants to login to a secure portion of the client system,the user will declare his/her intention through interaction with clientdisplay unit, and use of the interaction unit of the client display unitto input a request. As shown in FIG. 11, the interaction unit 151 willcommunicate the request to the processing unit 153 of the client displayunit, and the processing unit of the client display unit will thencommunicates the request to the processing unit 147 of the verificationsystem. The processing unit 109 of the user system will generate arequest to generate an Alpha Key (αk) combo consisting of a αk1 and αk2Keys that it sends to the key generator 157 of the client display unitvia the processing unit 147 of the verification system. The keygenerator of the client display unit transmits both αk1 & αk2 to theprocessing unit 147 of the verification system.

The processing unit 147 of the verification system then requests randomtext from the random text generator 143 of the verification system, andrequests a unique system & event identifier (USID) from the USIDgenerator 145 of the verification system. The random text generatorgenerates the random text and sends the random text to the processingunit 147 of the verification system. The USID generator generates theUSID and sends the USID to the processing unit of the verificationsystem. The USID generator is operable to identify to the verificationsystem, the user device and event that is trying to connect to thesecure area in the client system. The USID may be unique to each tab ina browser or in multiple browsers to identify and control the number ofbrowsers or tabs that are open for use by a user.

The processing unit 147 of the verification system combines the USID andrandom text that it receives with αk2 into a data string and convertsthe data string into a machine readable format, then sends this to theprocessing unit 153 of the client display unit. The interaction unit 151of the client display unit makes the information available to the readerunit 113 of the user system. As shown in FIG. 12, after the process ofFIG. 11 is completed the information is made available to the usersystem through the reader unit 113. The reader unit 113 may include oneor more sensors including any of the following auditory, visual,tactile, print, movement and other kind of sensors that may beincorporated in the client device or external to the client device butconnected thereto either via a wired connection or a wirelessconnection. The sensors may be utilized to obtain information relatingto the user.

The reader unit 113 then sends the information that it obtained to theprocessing unit 109 of the user system. The processing unit of the usersystem may separate the information it receives from the reader unit andmay hold that information. The processing unit 109 of the user systemwill request noise from the noise generator 107 of the user system. Thenoise generator will generate noise and will send the noise to theprocessing unit of the user system. The noise is used to mask theidentity of the information in transit.

If the user has previously been authenticated by the client system, theuser system may have a random Delta 1 Key (δk1).

The processing unit of the user system will send αk2 and δk1 to theverifier generator 105 of the user system. The processing unit will alsosend a request to the verifier generator of the user system requestingthat a new Beta Key be generated. In response to this request theverifier generator will generate Beta Key1 (βK1) and Beta Key2 (βK2)using αk2 and δk1. The verifier generator 105 will send βK1 and βK2 tothe processing unit 109 of the user system.

The processing unit of the user system will also access the storage unit111 of the user system and request Delta 1 Key and/or session codeand/or the generation of a session code. The storage unit 111 willprovide Delta 1 Key to the processing unit of the user system or willgenerate a session code and provide this to the processing unit of theuser system. For example, the processing unit 109 of the user system mayrequest that the random key generator 141 of the verification systemgenerate a random Delta 1 keys and/or a session code and provide this tothe processing unit 109, that may generate a hash value for δk1 or SCthat is provided.

The processing unit of the user system may generate a Manual InteractionCode (MIC) using the information obtained from each of the noisegenerator, the storage unit of the user system, and the verifiergenerator. The processing unit of the user system may send the MIC tothe interaction unit 103 of the user system. The interaction unit 103 ofthe client display unit will display the MIC to the user.

When the MIC is generated residual data will exist (the “post-MICdata”). The processing unit of the user system may conduct a symmetricor asymmetric encryption on the post-MIC Data. The processing unit ofthe user system may send the post-MIC data and the hash value to theprocessing unit 135 of the client system.

As shown in FIG. 13, once the MIC, the post-MIC data and the hash valueare created by the user system, the processing unit 135 of the clientsystem receives post-MIC data and the hash. The processing unit 135 ofthe client system sends the hash value to be stored temporarily in thestorage unit 133 of the client system. The post-MIC data is sent to theprocessing unit 153 of the client display unit.

The processing unit 153 of the client display unit combines αk1 andpost-MIC data as a package and sends this package to the key generator157 of the client display unit. The processing unit 153 requests thatthe key generator 157 of the client display unit generates a Gama key(γK). The γK is sent by the key generator of the client display unit tothe processing unit 153 of the client display unit.

The user is now required to interact with the interaction unit 151 ofthe client display unit. The user must manually enter the MIC. Onceentered, the MIC is then sent by the interaction unit of the clientdisplay unit to the processing unit 153 of the client display unit. Theprocessing unit 153 uses γK, MIC and package, to cause SC or δk1 to beavailable. The processing unit of the client display unit calculates thehash value for SC or δk1 and sends the hash value to the approval unit139 of the client system for verification.

Any of the information received or generated by the processing unit ofthe client display unit can be temporarily stored in the temporarystorage unit 155 of the client display unit at any point during theprocessing activities of the processing unit 153 of the client displayunit.

The processing unit 135 of the client system retrieves the hash valuetemporarily stored in the storage unit 133 of the client system. Theprocessing unit of the client system sends either the hash value of SCor δk1, and the value retrieved from storage to the approval unit 139 ofthe client system. The approval unit 139 compares the hash values todetermine a match.

If the hash values match then the approval unit 139 confirms the matchto the processing unit 135 of the client system.

As shown in FIG. 14, upon receiving this match confirmation, theprocessing unit 135 of the client system requests a Client SessionAccess Pass (CSAP) from the CSAP generator 131. The CSAP generator 131generates the CSAP which is sent to the storage unit 133 of the clientsystem to be stored temporarily. The CSAP generator 131 also sends theCSAP to the processing unit 147 of the verification system. Theprocessing unit 147 of the verification system sends the CSAP to theprocessing unit of the 153 client display unit. The processing unit 153of the client display unit sends CSAP to the processing unit 135 of theuser system. The processing unit 135 of the user system sends CSAP tothe approval unit 139 of the client system. The approval unit of theclient system confirms the CSAP. The processing unit of the user systemreceives notice of such confirmation and operates to permit the user toaccess secured portions of the client system.

If the approval unit 139 of the client system determines that the valuesdo not match, then the user, the user system and the client display unitare not authenticated.

The CSAP generator 131 of the client system may be utilized to testconditions relating to the authentication of the user; the user systemand the client display unit periodically through the generation of CSAP,the processing thereof by the processing unit of the client system andthe transfer of such CSAP to other processing units of the verificationsystem, user system, client display unit and storage of such CSAP in thestorage unit of the client system, user system and client display unit,in accordance with the method described herein. In any instance that theapproval unit of the client system determines that authenticationconditions are not met in relation to the CSAP, for example, such as adetermination that the CSAP received by the processing unit of theclient system and the stored CSAP do not match, then the authentication(i.e., CSAP authentication) of the user, the user device and the clientdisplay unit will be rescinded and access to the secure area terminatedfor the user, the user device and the client display unit.

CSAP conditions for authentication applied in embodiments of the presentinvention may include conditions relating to any of the following:dimensions, geo-temporal, machine learnt artificial intelligence,behavioral, or any other conditions.

Another embodiment of the present invention whereby the user uses theclient display unit to attempt to validate a transaction through accessto a secure portion of the client system is shown in FIG. 15. Theprocessing unit 153 of the client display unit sends a request to theprocessing unit 135 of the client system to validate a transaction. Uponsuch a request the processing unit 135 of the client system sends arequest to the challenge generator 137 of the client system to generatea challenge. Upon such a request the challenge generator 137 of theclient system will generate a challenge and may further apply a hashvalue to the result of the challenge, and save the solution and/or thehash value in the storage unit 133 of the client system. The challengegenerator of the client system will send the challenge to the processingunit 135 of the client system.

The processing unit 135 of the client system may apply symmetric and/orasymmetric encryption to the challenge. The processing unit 135 willsend the challenge to the processing unit 153 of the client displayunit. The processing unit 153 of the client display unit may decrypt thechallenge using the key provided to it, and will send the challenge tothe interaction unit 151 of the client display unit. In one embodimentof the present invention, the user may be required to interact with theinteraction unit 151 of the client display unit to find the solution tothe challenge. In another embodiment of the present invention, theprocessing unit 153 of the client display unit may solve the decryptedchallenge.

Once the user using the client display unit finds a solution to thechallenge, the user solution is sent to the processing unit 153 of theclient display unit. The processing unit 153 of the client display unitmay generate a hash value based upon the user solution, and theprocessing unit of the client display unit may further add eithersymmetric or asymmetric encryption to this hash value and/or to thesolution. The results of the processing by the processing unit of theclient display unit (e.g., a hash value or an encrypted hash value, or asolution or an encrypted solution) may be sent to the processing unit135 of the client system. The processing unit 135 of the client systemmay send a request to the storage unit 133 of the client system toretrieve the stored solution and/or the stored hash value. Upon such arequest the storage unit 133 of the client system will retrieve thestored solution and/or the stored hash value and send the storedsolution and/or stored hash value to the processing unit 135 of theclient system.

The processing unit 135 of the client system will decrypt any encryptedhash value or encrypted solution and/or non-encrypted hash values itreceives from the processing unit 153 of the client display unit. Theprocessing unit 135 of the client system will send the hash value and/orsolution it receives from the processing unit 153 of the client displayunit (in an unencrypted form), and the stored solution and/or the storedhas value, to the approval unit 139 of the client system for approval.The approval unit 139 of the client system will compare the receivedsolution to the stored solution, and/or the received hash value to thestored hash value.

If the received solution and/or hash values matches with the storedsolution and/or the hash values, the approval unit 139 will sendconfirmation to the processing unit 135 of the client system of a match.If the match is a positive the processing unit 135 of the client systemwill transmit the confirmation of the positive match to the clientsystem to confirm that the authentication of the transaction hascompleted successfully and the client system will thereby authorize thetransaction.

If the received solution and/or hash values does not match with thestored solution and/or the hash values, the approval unit 139 will sendnotice to the processing unit 135 of the client system that there is nomatch. The processing unit of the client system will transmit the noticeto the client system and advise the client system not to authenticatethe transaction.

In another embodiment of the present invention, the processing unit ofthe verification system can perform the functions described for theprocessing unit of the client system in accordance with FIG. 14. In suchan embodiment of the present invention a challenge generator unit and anapproval unit may be incorporated in either the client system or theverification system, and such challenge generator unit and approval unitwill have the same functions as described in accordance with FIG. 14 ofthe challenge generator 137 and the approval unit 139.

Another embodiment of the present invention whereby the user uses theuser system to attempt to validate a transaction is shown in FIG. 16. Insuch an embodiment of the present invention the processing unit 109 ofthe user system sends a request of the processing unit 135 of the clientsystem to validate a transaction. Upon such a request, the processingunit 135 of the client system sends a request to the challenge generator137 to generate a challenge. Upon such a request the challenge generator137 will generate a challenge, and will further apply hash value to theresult of the challenge (the solution of the challenge), and save thesolution and/or hash value in the storage unit 133 of the client system.

The processing unit 135 of the client system may apply symmetric and/orasymmetric encryption to the challenge. The processing unit 135 willsend the challenge, which may be encrypted, to the processing unit 109of the user system. The processing unit 109 of the user system maydecrypt the challenge, if the challenge is encrypted, and will send thechallenge to the interaction unit 103 of the user system. In oneembodiment of the present invention, the user may be required tointeract with the interaction unit 103 of the user system to find thesolution to the challenge. In another embodiment of the presentinvention, the processing unit 109 of the user system may solve thedecrypted challenge.

Once the user finds a solution to the challenge, the user solution issent to the processing unit 109 of the user system. The processing unit109 of the user system may generate a hash value based upon the usersolution, and the processing unit 109 of the user system may further addeither symmetric or asymmetric encryption to this hash value and/or tothe solution. The results of the processing by the processing unit 109of the user system (e.g., a hash value or an encrypted hash value, and asolution or an encrypted solution) may be sent to the processing unit135 of the client system. The processing unit 135 of the client systemmay send a request to the storage unit 133 of the client system toretrieve the stored solution and/or the stored hash value. Upon such arequest the storage unit 133 of the client system will retrieve thestored solution and/or the stored hash value and send the storedsolution and/or stored hash value to the processing unit 135 of theclient system.

The processing unit 135 of the client system will decrypt any encryptedhash value or encrypted solution it receives from the processing unit109 of the user system. The processing unit 135 of the client systemwill send the hash value and solution it receives from the processingunit 109 of the user system (in an unencrypted form), and the storedsolution and/or the stored has value, to the approval unit 139 of theclient system for approval. The approval unit 139 of the client systemwill compare the received solution to the stored solution, and/or thereceived hash value to the stored hash value.

If the received solution matches with the stored solution and/or thereceived hash value matches with the stored hash value, then theapproval unit 139 will send confirmation to the processing unit 135 ofthe client system of a match. The processing unit 135 of the clientsystem will transmit the confirmation of a match to the client system toconfirm that the authentication of the transaction is completed andsuccessful.

If the received solution matches with the stored solution and/or thereceived hash value matches with the stored hash value, then theapproval unit 139 will send notice to the processing unit of the clientsystem that there is no match. The processing unit of the client systemwill transmit the notice to the client system and advise the clientsystem not to authenticate the transaction.

In another embodiment of the present invention, the processing unit ofthe verification system can perform the functions described for theprocessing unit of the client system in accordance with FIG. 16. In suchan embodiment of the present invention a challenge generator unit and anapproval unit may be incorporated in either the client system or theverification system, and such challenge generator unit and approval unitwill have the same functions as described in accordance with FIG. 16 ofthe challenge generator 137 and the approval unit 139.

A system and network for authentication may comprise one or more firstpeers, one or more servers, and one or more second peers, eachcomprising at least a processor and a transmitter/receiver. One or morefirst peers and one or more second peers may additionally comprise arespective memory. In some embodiments, each of one or more first peersand one or second peers may comprise a visual display. One or moreservers may additionally comprise a database.

A transmitter/receiver of each of a first peer, a second peer, and aserver may be configured to transmit and receive information from anexogenous source. In some embodiments, a first peer may be configured totransmit and receive information from a server, a server may beconfigured to transmit and receive information from both a first peerand a second peer, and a second peer may be configured to transmit andreceive information from a server. A memory of a first peer and a secondpeer and a database of a server may be configured to store informationand to allow information to be retrieved. A visual display mayadditionally comprise a means for a user to interact with a display,e.g. enter data, select characters, select objects, etc.

A processor of a first peer, a second peer, or a server may comprise aprocessing migrator, a data manipulator, a data converter, a processinggenerator, and a processing verifier. A processing migrator may beconfigured to migrate data from one component within a first peer, asecond peer, or a server to another component within a first peer, asecond peer, or a server. By way of example, and not limitation, aprocessing migrator may be configured to move data from a memory of afirst peer to a processor of a first peer, or from a processor of asecond peer to a transmitter/receiver of a second peer. A datamanipulator may be configured to manipulate data, e.g. combine,separate, separate and recombine, reorder, etc. By way of example, andnot limitation, a data manipulator of a first peer may be configured toseparate a one or more strings of characters into a first portion and asecond portion, or a data manipulator of a server may be configured tocombine a first portion of data with a second portion of data to producea single packet of data.

A data converter may be configured to convert a first string ofcharacters into a second string of characters, wherein each of a firststring of characters and a second string of characters may be differentin any one or more of length, composition, or arrangement. In someembodiments, a data converter may be configured to apply hash algorithmsto a first string of characters. In other embodiments, a data convertermay be configured to apply encryption protocols to a first string ofcharacters. In yet other embodiments, a data converter may be configuredto apply decryption protocols to a first string of characters. In otherembodiments still, a data converter may be configured to apply anycombination of hash algorithms, encryption protocols, decryptionprotocols, or any other known method of data conversion to a firststring of characters to produce a second string of characters.

A processing generator may be configured to produce data. In someembodiments, data may comprise a one or more strings of characters ofany length and may comprise bar codes and the like. In some embodiments,data may be produced in either a random manner or in a directed manner.A processing verifier may be configured to compare two or more data anddetermine if those data are identical or different. In some embodiments,a processing verifier and a processing generator may be paired todetermine if a first string of characters and a second string ofcharacters are identical and generate a response based on the identityof a first and second string of characters.

An authentication method may comprise a registration method 1700 and auser log-in method 2000. In some embodiments, a registration method 1700may comprise creating one or more keys, distributing one or more keys,storing one or more keys on a local database, and storing one or morekeys on a server database. Illustrated in FIG. 17, a registration method1700 may additionally comprise communication between a first peer 1701,a server 1750, and at least one second peer 1775.

In some embodiments of a registration method 1700, a server 1750 mayreceive a registration request 1702 from a first peer 1701. A server1750 may send registration data 1751 to a first peer 1701. Registrationdata 1751 may comprise any data required for a registration method 1700.In some embodiments, registration data 1751 may comprise a clientregistration code 1703. A client registration code 1703 may be made upof one or more characters comprising letters, numbers, symbols, or anycombination thereof, and may be generated by a server 1750. In otherembodiments, registration data comprises user selection objects. In yetother embodiments, registration data may comprise a combination of oneor more of client registration codes 1703, user selection objects, andany other data required for registration.

A registration method 1700 may further comprise generating a server key1705 and a client key 1706 from user input 1704. In some embodiments, aserver key 1705 and a client key 1706 are used to generate aregistration key 1707. In other embodiments, a server key 1705, a clientkey 1706, and at least one client registration code 1703 are used togenerate a registration key 1707. Other embodiments may comprisedifferent combinations of client keys 1706, server keys 1705, and clientregistration codes 1703 being used to generate registration keys 1707.Some information, e.g. a client key 1706, a client registration code1703, may be stored in the memory 1708 of a first peer 1701. Further, aregistration method 1700 may comprise transferring information from afirst peer 1701 to a server 1750. In some embodiments, a registrationkey 1707 and a server key 1705 are transferred to a server 1750.

A registration method 1700 may comprise receiving information from afirst peer 1701 at a server 1750. In some embodiments, informationreceived at a server 1750 may comprise a registration key 1707 and aserver key 1705. A server 1750 may generate a recipient code 1752.Further, a server 1750 may generate a sender code 1754. Even further, aserver 1750 may generate a distribution code 1756. A server key 1705,recipient code 1752, and sender code 1754 may be used to generate adistribution key 1753. In some embodiments, a distribution key 1753 maybe generated from any one or more of server keys 1705, recipient codes1752, or sender codes 1754, or any combination therein. Someinformation, e.g. a recipient code 1752, a distribution key 1753, may bestored in the database 1757 of a server 1750. A registration method 1700may further comprise transferring information from a server 1750 to atleast one second peer 1775. In some embodiments, a distribution key 1753and a distribution code 1756 are transferred to at least one second peer1775.

A registration method 1700 may further comprise storing one or more keyson a local database. Illustrated in FIG. 17, at least one second peer1775 may receive information from a server 1750. In some embodiments,information may comprise a distribution key 1753 and a distribution code1756. A second peer may generate a deposit code 1776. Further, adistribution key 1753 and a deposit code 1776 may be used to generate adeposit key 1777. In some embodiments, a deposit key 1777 may begenerated using only a distribution key 1753, only a deposit code 1776,or any combination of distribution keys 1753 and deposit codes 1776.Some information, e.g. a distribution key 1753, a deposit key 1777, adistribution code 1756 may be stored in the memory 1758 of a second peerdevice 1775. A registration method 1700 may further comprisetransferring information from a second peer 1775 to a server 1750. Insome embodiments, a deposit key 1777 and a distribution code 1756 aretransferred to a server 1750.

A registration method 1700 may comprise receiving information from asecond peer 1775 and storing that information in a local database. Insome embodiments, a server 1750 receives information from a second peer1775. Information received may comprise a deposit key 1777, adistribution code 1756, and other information needed for storage ofinformation by the server 1750 or for identification of the second peer1775.

Referring now to FIG. 18, creating one or more keys 1800, according tosome embodiments, may occur in a first peer 1801. A first peer 1801 maybe any IoT device, i.e. any device that may connect to a network andhave the ability to transmit data, including but not limited to cellphones, personal assistants, buttons, home security systems, appliances,and the like. A first peer 1801 may request registration from a server1850. According to some embodiments, a server 1850 may transmitregistration data to a first peer 1801. Registration data may bereceived by a transmitter/receiver 1841 of a first peer 1801 and maycomprise any data necessary to generate one or more keys 1800 at a firstpeer 1801. In some embodiments, registration data may comprise a clientregistration code 1803. In other embodiments, registration data maycomprise a client registration code 1803 and additional data which mayserve as a precursor to user input 1804. A client registration code 1803may comprise a one or more strings of characters of any length.

User input 1804 may comprise any form of user-generated data whichcomprises discreet units of information. In some embodiments, user input1804 comprises biometric data, e.g. fingerprint, iris, etc. In thoseembodiments, biometric data may be split into discreet units ofinformation comprising identifiers. Identifiers may be converted intounique selection codes 1809. In other embodiments, user input 1804 maycomprise any number of spatial and/or temporal data. Spatial and/ortemporal data may be split into discreet units of information comprisingidentifiers. Identifiers may be converted into unique selection codes1809. In yet other embodiments, user input 1804 may comprise acombination of biometric data and spatial and/or temporal data, each ofwhich may be used to generate unique selection codes 1809.

In other embodiments, user input 1804 may comprise one or more selectionobjects. One or more selection objects may be images, icons, tokens,buttons, or any other object that allows a user to select one or moreselection objects from a group of selection objects. In someembodiments, selection objects may be received at a transmitter/receiver1841 and a processing migrator 1842 may migrate selection objects to avisual display 1843. Upon selection by a user on a visual display 1843,selection objects may be converted into selection codes 1809 which maycomprise any number of characters, e.g. letters, numbers, symbols. In aspecific embodiment, selection objects are images that may be receivedfrom a server 1850. Each image is assigned a unique selection code 1809,wherein user selection of a combination of selection objects produces auser input 1804 comprising a combination of selection codes 1809 that isunique to the user's selection of selection objects. In someembodiments, any combination of biometric data, spatial and/or temporaldata, and selection objects may comprise user input 1804.

According to some embodiments, a user may generate user input 1804comprising two or more selection codes 1809, wherein the number ofselection codes is equal to n. A data manipulator 1844 may be configuredto separate selection codes into two or more groups. In someembodiments, a data manipulator 1844 may be configured to separateselection codes 1809 into a first group 1810 and a second group 1811,wherein a first group 1810 comprises between one and n−1 selection codes1809 and a second group 1811 comprises between one and n−1 selectioncodes 1809. Each selection code 1809 in a first group 1810 and a secondgroup 1811 may be individually converted 1812 into a one or more stringsof characters, by a data converter 1845, resulting in a first group ofconverted selection codes 1813 and a second group of converted selectioncodes 1815. In some embodiments, conversion 1812 may comprise using hashalgorithms. In other embodiments, conversion 1812 may comprise usingencryption methods. Yet other embodiments may comprise conversion 1812using a combination of hash algorithms and encryption methods. A firstgroup of converted selection codes 1813 may be used to generate a clientpre-key 1814. Individual converted selection codes comprising a firstgroup of converted selection codes 1813 may be combined by a datamanipulator 1844 to form one or more strings of characters comprising aclient pre-key 1814. In some embodiments, individual converted selectioncodes are combined through concatenation of units. Concatenation maycomprise using each of the individual converted selection codes as aunit or may comprise using pieces of each individual converted selectioncode as a unit. A client pre-key 1814 may be converted 1812 to a clientkey 1806 by a data converter 1845. In some embodiments, conversion 1812may comprise using hash algorithms. In other embodiments, conversion1812 may comprise using encryption methods. Yet other embodiments maycomprise conversion 1812 using a combination of hash algorithms andencryption methods. A client key 1812 may be stored in a memory 1808 ofa first peer 1801 by a processing migrator 1842.

A second group of converted selection codes 1815 may be used to generatea server pre-key 1816. Individual converted selection codes comprising asecond group of converted selection codes 1815 may be combined by a datamanipulator 1844 to form one or more strings of characters comprising aserver pre-key 1816. In some embodiments, individual converted selectioncodes may be combined through concatenation of units. Concatenation maycomprise using each of the individual converted selection codes as aunit or may comprise using pieces of each individual converted selectioncode as a unit. A server pre-key 1816 may be converted 1812 to a serverkey 1805 by a data converter 1845. In some embodiments, conversion 1812may comprise using hash algorithms. In other embodiments, conversion1812 may comprise using encryption methods. Yet other embodiments maycomprise conversion 1812 using a combination of hash algorithms andencryption methods.

According to some embodiments, a registration key 1807 may be generated.Each of a client key 1806 and a server key 1805 may be separated by adata manipulator 1844 into a client key first part 1817, a client keysecond part 1818, a server key first part 1819, and a server key secondpart 1820. In some embodiments, a client key 1806 may be separated intothree or more parts. Likewise, a server key 1805 may be separated intothree or more parts. A client key first part 1817 and a client keysecond part 1818 may comprise different portions of the characters thatcomprise a client key 1806. In a specific embodiment, each of a clientkey first part 1817 and a client key second part 1818 may be one half ofa client key 1806. A server key first part 1819 and a server key secondpart 1820 may comprise different portions of the characters thatcomprise a server key 1805. In a specific embodiment, each of a serverkey first part 1819 and a server key second part 1820 may be one half ofa server key 1805. A client key first part 1817, a client key secondpart 1818, a server key first part 1819, and a server key second part1820 may be combined by a data manipulator 1844 through concatenation ofunits to form one or more strings of characters comprising a firstpre-key 1821. Concatenation by a data manipulator 1844 may compriseusing each of a client key first part 1817, a client key second part1818, a server key first part 1819, and a server key second part 1820 asa unit or may comprise using pieces of a client key first part 1817, aclient key second part 1818, a server key first part 1819, and a serverkey second part 1820 as a unit. Further, concatenation may compriseusing any combination of parts generated by separation of a client key1806 or a server key 1805. A first pre-key 1821 may be converted 1812 bya data converter 1845 into a one or more strings of characterscomprising a second pre-key 1822. In some embodiments, conversion 1812may comprise using hash algorithms. In other embodiments, conversion1812 may comprise using encryption methods. Yet other embodiments maycomprise conversion 1812 using a combination of hash algorithms andencryption methods. A second pre-key 1822 may be used to generate aregistration pre-key 1823. According to some embodiments, a secondpre-key 1822 and a client registration code 1803 may be concatenated bya data manipulator 1844 to form one or more strings of characterscomprising a registration pre-key 1823. Concatenation may comprise usingeach of a second pre-key 1822 and a client registration code 1803 as aunit or may comprise using pieces of a second pre-key 1822 and a clientregistration code 1803 as a unit. A registration pre-key 1823 may beconverted 1812 by a data converter 1845 into a one or more strings ofcharacters comprising a registration key 1807. In some embodiments,conversion 1812 may comprise using hash algorithms. In otherembodiments, conversion 1812 may comprise using encryption methods. Yetother embodiments may comprise conversion 1812 using a combination ofhash algorithms and encryption methods.

A first peer 1801 may transmit information to a server 1850. Accordingto some embodiments, a processing migrator 1842 of a first peer 1801 maymigrate a registration key 1807 and a server key 1805 to atransmitter/receiver 1841 of a first peer 1801, which may transmit aregistration key 1807 and a server key 1805 to a server 1850. In otherembodiments, a transmitter/receiver 1841 of a first peer 1801 maytransmit a registration key 1807, a server key 1805, and otherinformation necessary for a registration method to a server 1850.

A registration method may further comprise distributing one or more keys1900. Illustrated in FIG. 19, a transmitter/receiver 1941 of a server1950 may receive information from a first peer 1901. According to someembodiments, a transmitter/receiver 1941 of a server 1950 may receive aregistration key 1907 from a first peer 1901. A transmitter/receiver1941 of a server 1950 may receive a server key 1905 from a first peer1901. A transmitter/receiver 1941 of a server 1950 may receive both aregistration key 1907 and a server key 1905 from a first peer 1901. Aprocessing migrator 1942 may migrate a registration key 1907 and aserver key 1905 to a processor of a server 1950. A registration key 1907may be stored in a database 1957 of a server 1950 by a processingmigrator 1942. A processing generator 1946 of a server 1950 may generatea peer list 1958. A peer list 1958 may comprise a list of peer devices,e.g. a first peer 1901, a second peer 1975, on the network. A peer listmay also comprise recipient codes 1952 and distribution codes 1956,which may comprise a one or more strings of characters of any length.Additionally, a processing generator 1946 of a server 1950 may generatea sender code 1954, which may also comprise a one or more strings ofcharacters of any length.

According to some embodiments, a server 1950 may receive a registrationkey 1907 from a first peer 1901. A registration key 1907 may be used togenerate any number of registration key subparts. A data manipulator maygenerate registration key subparts from a registration key 1907. Inthese embodiments, a registration key 1907 may comprise any number ofcharacters equal to n. Each registration key subpart may comprise anynumber or combination of characters equal to n−1. A server 1950 maygenerate one or more random strings of characters. Each of aregistration subpart may be concatenated with one or more random stringsof characters by a data manipulator 1944. In some embodiments,concatenated strings may be converted 1912. Each generated concatenatedstring or converted concatenated string may be transmitted to one ormore second peers 1975.

A server 1950 may receive a server key 1908 from a first peer 1901. Aserver key 1908 may be used to generate any number of server keysubparts. A data manipulator may generate server key subparts from aserver key 1908. In these embodiments, server key 1908 may comprise anynumber of characters equal to n. Each server key subpart may compriseany number or combination of characters equal to n−1. A server 1950 maygenerate one or more random strings of characters. Each of a server keysubpart may be concatenated with one or more random strings ofcharacters by a data manipulator 1944. In some embodiments, concatenatedstrings may be converted 1912. Each generated concatenated string orconverted concatenated string may be transmitted to one or more secondpeers 1975.

A data manipulator 1944 of a server 1950 may generate a distributionpre-key 1959 by combining any combination of a server key 1905, arecipient code 1952, a sender code 1954, a distribution code 1956, or aregistration key 1907. In some embodiments, a distribution pre-key iscomprised of a server key 1905, a sender code 1954, and a recipient code1952, which may be combined through concatenation of units to form oneor more strings of characters. Concatenation may comprise using each ofa server key 1905, a sender code 1954, and a recipient code 1952 as aunit or may comprise using pieces of a server key 1905, a sender code1954, and a recipient code 1952 as a unit. A distribution pre-key 1959may be converted 1912 by a data converter 1945 into a one or morestrings of characters comprising a distribution key 1953. In someembodiments, conversion 1912 may comprise using hash algorithms. Inother embodiments, conversion 1912 may comprise using encryptionmethods. Yet other embodiments may comprise conversion 1912 using acombination of hash algorithms and encryption methods. A distributionkey 1953 may be stored in a database 1957 of a server 1950 by aprocessing migrator 1942. A server 1950 may be configured to transmitinformation to a second peer 1975. In some embodiments, a processingmigrator 1942 of a server 1950 may migrate a distribution key 1953 and adistribution code 1956 to a transmitter/receiver 1941 of a server 1950.In other embodiments, a transmitter/receiver 1941 of a server 1950 maytransmit a distribution key 1953, a distribution code 1956, and otherinformation necessary for a registration method to a second peer 1975.In some embodiments, a server 1950 may store any combination of aregistration key 1907, a server key 1905, and a distribution key 1953 ata database 1957 of a server 1950.

A server 1950 may generate more than one distribution keys 1953 andtransmit data to more than one second peer 1975. In some embodiments, apeer list 1958 may comprise a list of more than one second peers 1975 onthe network. A second peer may comprise any IoT device, server, or anydevice that is on a network and capable of transmitting and receivingdata from a server 1950. A server 1950 may generate a uniquedistribution code 1956 for each second peer 1975. A server 1950 maygenerate a unique recipient code 1952 for each second peer 1975. Inthese embodiments, a distribution key 1953 created for each second peer1975 may be different from distribution keys 1953 created for othersecond peers 1975, although underlying server keys 1905 received from afirst peer 1901 may be identical.

According to some embodiments, a registration key 1907 may be used togenerate a distribution pre-key 1959. In these embodiments, anycombination of a registration key 1907, a sender code 1954, a recipientcode 1952, and a server key 1905 may be used to generate a distributionpre-key 1959.

Referring now back to FIG. 17, a registration method 1700 may comprisestoring one or more keys on a local database. According to someembodiments, a second peer 1775 may be configured to receive andtransmit information to a server 1750 through a transmitter/receiver ofa second peer 1775. A second peer 1775 may receive a distribution key1753 from a server 1750 through a transmitter/receiver of a second peer1775. A second peer 1775 may receive a distribution code 1756 from aserver 1750. In some embodiments, a second peer 1775 may receive adistribution key 1753 and a distribution code 1756 from a server 1750. Adistribution key 1753 and a distribution code 1756 may be stored in amemory 1778 of a second peer 1775. A second peer 1775 may generate adeposit code 1776. A deposit code 1776 may be a one or more strings ofcharacters of any length and may be generated in a random fashion.Alternatively, a deposit code 1776 may be generated by a server 1750 andreceived by a second peer 1775. A deposit code 1776 and a distributionkey 1753 may be combined through concatenation of units to form one ormore strings of characters comprising a deposit pre-key 1779.Concatenation may comprise using each of a deposit code 1776 and adistribution key 1753 as a unit or may comprise using pieces of depositcode 1776 and a distribution key 1753 as a unit. A deposit pre-key 1779may be converted 1712 into a one or more strings of characterscomprising a deposit key 1777. In some embodiments, conversion 1712 maycomprise using hash algorithms. In other embodiments, conversion 1712may comprise using encryption methods. Yet other embodiments maycomprise conversion 1712 using a combination of hash algorithms andencryption methods. A deposit key 1777 may be stored in a memory 1778 ofa second peer 1775. In some embodiments, a second peer 1775 may transmita deposit key 1777 and a distribution code 1756 to a server 1750. Inother embodiments, a second peer 1775 may transmit a deposit key 1777, adistribution code 1756, and any other information necessary for aregistration method 1700 to a server 1750.

A registration method 1700 may further comprise storing one or more keyson a server database. Shown in FIG. 19, a transmitter/receiver 1941 of aserver 1950 may receive information from a second peer 1975. In someembodiments, a transmitter/receiver 1941 of a server 1950 may receive adistribution code 1956. In some embodiments, a transmitter/receiver 1941of a server 1950 may receive a deposit key 1977. In other embodiments, atransmitter/receiver 1941 of a server 1950 may receive a distributioncode 1956 and a deposit key 1977. In yet other embodiments, atransmitter/receiver 1941 of a server 1950 may receive a distributioncode 1956, a deposit key 1977, and any other information necessary for aregistration method. A distribution code 1956 and a deposit key 1977 maybe stored in a database 1957 of a server 1950 by a processing migrator1942.

In a specific embodiment, a registration method 1700 may comprisecreating one or more keys, distributing one or more keys, storing one ormore keys on a local database, and storing one or more keys on a serverdatabase. Illustrated in FIG. 17, a registration method 1700 may beginwith a request for registration 1702 from a first peer 1701. A requestfor registration 1702 may be transmitted to and received by one or moreservers 1750. One or more servers may transmit registration data 1751 toa first peer 1701. Referring now to FIG. 18, a specific embodiment maycomprise a first peer 1801 receiving registration data from a server1850. Registration data may comprise a client registration code 1803 andone or more selection objects. A client registration code 1803 maycomprise a single, eight-digit string of characters. Selection objectsmay comprise a number of images. In a specific embodiment, selectionobjects may comprise a number of selection objects equal to 60. Eachselection object may contain a unique selection code 1809. A selectioncode 1809 may comprise a one or more strings of characters, and in aspecific embodiment, each selection code may comprise a string of fivecharacters. A user may select a number of selection objects fromselection objects received by a server 1850. In a specific embodiment, auser may select six selection objects. A user's selection of selectionobjects may generate user input 1804 comprising a collection ofselection codes 1809 that may be chosen by selecting specific selectionobject associated with each selection code 1809. In a specificembodiment, user input 1804 comprises six, five-character selectioncodes 1809.

User input 1804 may be separated into a first group 1810 and a secondgroup 1811. In a specific embodiment, each of a first group 1810 and asecond group 1811 comprises three different selection codes 1809. Eachselection code 1809 comprising a first group 1810 and a second group1811 may be converted 1812 into one or more strings of characters. In aspecific embodiment, each selection code 1809 may be converted using ahash algorithm and may collectively comprise a first group of convertedselection codes 1813 and a second group of converted selection codes1815, respectively. Each of a first group of converted selection codes1813 and a second group of converted selection codes 1815 may becombined to generate each of a client pre-key 1814 and a server pre-key1816, respectively. In a specific embodiment, three converted selectioncodes comprising a first group of converted selection codes 1813 may beconcatenated to produce one or more strings of characters comprising aclient pre-key 1814. Likewise, three converted selection codescomprising a second group of converted selection codes 1815 may beconcatenated to produce one or more strings of characters comprising aserver pre-key 1816. A client pre-key 1814 and a server pre-key 1816 maybe converted 1812 to a client key 1806 and a server key 1805,respectively. In a specific embodiment, conversion 1812 comprises usinga hash algorithm.

A registration key 1807 may be generated using a combination of clientkey 1806, server key 1805, and client registration code 1803. In aspecific embodiment, a client key 1806 and server key 1805 are separatedinto a first part 1817 and 1819, and a second part 1818 and 1820,respectively. A first pre-key 1821 may be generated by combining anypart of a client key 1806 and any part of a server key 1805 byconcatenation to form one or more strings of characters. A first pre-key1821 may be converted 1812 into one or more strings of characterscomprising a second pre-key 1822. In a specific embodiment, conversion1812 comprises using a hash algorithm. A registration pre-key 1823 maybe generated by combining a client registration code 1803 and a secondpre-key 1822 by concatenation to form one or more strings of characters.A registration pre-key 1823 may be converted 1812 to a registration key1807, where conversion 1812 comprises using a hash algorithm. In aspecific embodiment, a client key 1806 and a client registration code1803 may be stored in a memory 1808 of a first peer 1801. Further, aserver key 1805 and a registration key 1807 may be transmitted to one ormore servers 1850.

A registration method may comprise distributing one or more keys. In aspecific embodiment, shown in FIG. 19, a server 1950 may receive aregistration key 1907 and a server key 1905 from a first peer 1901. Aregistration key may be stored in a database 1957 of a server 1950. Aserver 1950 may generate a peer list 1958, which may comprise a list ofsecond peers 1975 on the network. For each of the second peers 1975, aserver 1950 may generate a recipient code 1952 and a distribution code1956. In a specific embodiment, a recipient code 1952 and a distributioncode 1956 may be unique to both a specific second peer 1975 and aspecific transaction. Additionally, a server 1950 may generate a sendercode 1954 that may be unique to a particular server 1950. In a specificembodiment, a recipient code 1952, a sender code 1954, and a server key1905 may be combined through concatenation to produce one or morestrings of characters comprising a distribution pre-key 1959. Adistribution pre-key 1959 may be converted 1912 into a distribution key1953. In a specific embodiment, conversion 1912 may comprise using ahash algorithm. In some embodiments, multiple unique distribution keys1953 may be generated, each comprising a different recipient code 1952and having a different associated distribution code 1956 from a peerlist 1958, wherein each unique distribution key 1953 may be ultimatelytransmitted to a different second peer 1975. In a specific embodiment,multiple unique distribution keys 1953 are generated from an identicalserver key 1905 and each of the unique distribution keys 1953 istransmitted to a separate second peer 1975 on a network.

A registration method may further comprise storing one or more keys on alocal database, illustrated in FIG. 17. In a specific embodiment, asecond peer 1775 may receive a distribution key 1753 and a distributioncode 1756 from a server 1750. In this embodiment, a second peer 1775 maybe one of several second peers 1775 in a network to receive distributionkeys 1753 and distribution codes 1756 arising from a same transactionbetween a first peer 1701 and a server 1750 discussed above. A secondpeer 1775 may store a distribution key 1753 and a distribution code 1756in a memory 1778 of a second peer 1775. Further, a second peer 1775 maygenerate a deposit code 1776. In a specific embodiment, a deposit code1776 comprises a single string of eight characters. A deposit code 1776and a distribution key 1753 may be combined through concatenation toproduce one or more strings of characters comprising a deposit pre-key1779. A deposit pre-key 1779 may be converted 1712 to a deposit key1777. In a specific embodiment, conversion 1712 comprises using a hashalgorithm. A second peer 1775 may transmit information to one or moreservers 1750. In a specific embodiment, several second peers 1775 maytransmit information to a server 1750. Information may comprise adistribution code 1756, a deposit key 1777, and any other informationnecessary to perform a registration process 1700.

A registration method 1700 may comprise storing one or more keys on aserver database. In some embodiments, a server 1750 may be configured toreceive information from one or more second peers 1775. In a specificembodiment, a server 1750 may receive information from several secondpeers 1775, information comprising distribution codes 1756 and depositkeys 1777. A server 1750 may store distribution codes 1756 and depositkeys 1777 in a database 1757. Referring now to FIG. 19, distributioncodes 1956 and deposit keys 1977 may be stored on a peer list 1958stored inside a database 1957. In a specific embodiment, distributioncodes 1956 and deposit keys 1977 are paired with stored distributionkeys 1953 and recipient codes 1952 which may be specific to atransaction conducted between a first peer 1901, a server 1950, and aspecific second peer 1975.

An authentication method may comprise a login method, illustrated inFIG. 20. A login method 2000 may comprise creating one or more loginkeys, distributing one or more verification keys, verifying averification key in a local database, and validating a verificationprocess. Additionally, a login method 2000 may comprise communicationbetween one or more first peers 2001, one or more servers 2050, and oneor more second peers 2075.

A login method 2000 may comprise a first peer 2001, wherein the firstpeer may be configured to interact with a user. A first peer 2001 mayrequest login 2002 and a login request 2002 may be transmitted to one ormore servers 2050. A server 2050 may receive a login request 2002 andgenerate login data 2051. In some embodiments, login data 2051 maycomprise a login salt 2024. A login salt may be made up of one or morecharacters comprising letters, numbers, symbols, or any combinationthereof. In some embodiments, login data 2051 may comprise userselection objects. In other embodiments, login data 2051 may compriseone or more login salts 2024 and user selection objects, and any otherdata required for a login method 2000.

Creating one or more login keys may further comprise generating a serverkey 2005 and a client key 2006 from user input 2004. In someembodiments, a server key 2005 and a client key 2006 may be used togenerate a login key 2099. In other embodiments, a server key 2005, aclient key 2006, and at least login salt 2024 may be used to generate alogin key 2099. Other embodiments may comprise different combinations ofclient keys 2006, server keys 2005, and login salts 2024 being used togenerate login keys 2099. Some information, e.g. a client key 2006, alogin salt 2024, may be stored in the memory 2008 of a first peer 2001.Further, creating one or more login keys may comprise transferringinformation from a first peer 2001 to a server 2050. In someembodiments, a login key 2099 and a server key 2005 are transferred to aserver 2050.

Also shown in FIG. 20, distributing one or more verification keys maycomprise receiving information from a first peer 2001 at a server 2050.In some embodiments, information received at a server 2050 may comprisea login key 2099 and a server key 2005. A server 2050 may generate arecipient code 2052. Further, a server 2050 may generate a sender code2054. Even further, a server 2050 may generate a distribution code 2056.A server key 2005, recipient code 2052, and sender code 2054 may be usedto generate a verification key 2062. In some embodiments, a verificationkey 2062 may be generated from one or more server keys 2005, recipientcodes 2052, verification salts 2024 or sender codes 2054, or anycombination therein. Some information, e.g. a recipient code 2052, averification key 2062, may be stored in the database 2057 of a server2050. In some embodiments, a verification key 2062 may not be stored inthe database 2057 of a server 2050. Distributing one or moreverification keys may further comprise transferring information from aserver 2050 to at least one second peer 2075. In some embodiments, averification key 2062 and a distribution code 2056 are transferred to atleast one second peer 2075.

A login method 2000 may further comprise verifying one or moreverification keys on a local database. Illustrated in FIG. 20, at leastone second peer 2075 may receive information from a server 2050. In someembodiments, information may comprise a verification key 2062 and adistribution code 2056. In other embodiments, information may comprise averification key 2062, a distribution code 2056, and a verification salt2063. A second peer 2075 may use any combination of a distribution code2056 and a verification key 2062 to locate and confirm that acorresponding distribution key may be stored in a memory 2078 of asecond peer 2075. A stored distribution key may be used to generateconfirmation key 2081. In some embodiments, a stored distribution key2053 and a verification salt 2063 received from a server 2050 may beused to generate a confirmation key 2081. A second peer 2075 maytransmit information to a server 2050, which may comprise anycombination of a confirmation key 2081, a distribution code 2056, andany other information that may be necessary for a login method 2000.

Validating a verification process may comprise receiving informationfrom a second peer 2075 and comparing received information againstinformation stored in a database 2057 of a server 2050. In someembodiments, a server 2050 receives information from a second peer 2075.Information received may comprise a confirmation key 2081, a result, adistribution code 2056 and other information needed for storage orcomparison of information by the server 2050 or for identification ofthe second peer 2075.

Shown in FIG. 21, creating one or more login keys 2100, according tosome embodiments, may occur in a first peer 2101. A first peer 2101 maybe any IoT device, i.e. any device that may connect to a network andhave the ability to transmit data, including but not limited to cellphones, personal assistants, buttons, home security systems, appliances,and the like. A first peer 2101 may request login from a server 2150.According to some embodiments, a transmitter/receiver of a server 2150may transmit login data to a first peer 2101. Login data may be receivedby a transmitter/receiver 2141 of a first peer 2101 and may comprise anydata necessary to initiate a login method at a first peer 2101. In someembodiments, login data may comprise a login salt 2124. In otherembodiments, login data may comprise a login salt 2124 and additionaldata which may serve as a precursor to user input 2104. A login salt2124 may comprise a one or more strings of characters of any length.

Also shown in FIG. 21, user input 2104 may comprise any form ofuser-generated data which comprises discreet units of information. Insome embodiments, user input 2104 comprises biometric data, e.g.fingerprint, iris, etc. In those embodiments, biometric data may besplit into discreet units of information comprising identifiers.Identifiers may be converted into unique selection codes 2109.

In other embodiments, user input 2104 may comprise one or more selectionobjects. One or more selection objects may be images, icons, tokens,buttons, or any other object that allows a user to select one or moreselection objects from a group of selection objects. Selection objectsmay be displayed on a visual display 2143 of a first peer 2101 and maybe converted into selection codes 2109 which may comprise any number ofcharacters, e.g. letters, numbers, symbols. In a specific embodiment,selection objects are images that may be received from a server 2150.Each image is assigned a unique selection code 2109, wherein userselection of a combination of selection objects produces a user input2104 comprising a combination of selection codes 2109 that is unique tothe user's selection of selection objects.

According to some embodiments, a user may generate user input 2104comprising two or more selection codes 2109, wherein the number ofselection codes is equal to n. Selection codes 2109 may be separated bya data manipulator 2144 into a first group 2110 and a second group 2111,wherein a first group 2110 comprises between one and n−1 selection codes2109 and a second group 2111 comprises between one and n−1 selectioncodes 2109. Each selection code 2109 in a first group 2110 and a secondgroup 2111 may be individually converted 2112 by a data converter 2145into a one or more strings of characters, resulting in a first group ofconverted selection codes 2113 and a second group of converted selectioncodes 2115. In some embodiments, conversion 2112 may comprise using hashalgorithms. In other embodiments, conversion 2112 may comprise usingencryption methods. Yet other embodiments may comprise conversion 2112using a combination of hash algorithms and encryption methods. A firstgroup of converted selection codes 2113 may be used to generate a clientpre-key 2114. Individual converted selection codes comprising a firstgroup of converted selection codes 2113 may be combined by a datamanipulator 2144 to form one or more strings of characters comprising aclient pre-key 2114. In some embodiments, individual converted selectioncodes may be combined through concatenation of units. Concatenation maycomprise using each of the individual converted selection codes as aunit or may comprise using pieces of each individual converted selectioncode as a unit. A client pre-key 2114 may be converted 2112 by a dataconverter 2145 to a client key 2106. In some embodiments, conversion2112 may comprise using hash algorithms. In other embodiments,conversion 2112 may comprise using encryption methods. Yet otherembodiments may comprise conversion 2112 using a combination of hashalgorithms and encryption methods. A client key 2106 may be stored by aprocessing migrator 2147 in a memory unit 2108 of a first peer 2101. Aclient key 2106 generated by a login method may be compared by aprocessing verifier 2147 to a client key 2106 stored in a memory 2108 ofa first peer 2101 during a registration process for identity.

A second group of converted selection codes 2115 may be used to generatea server pre-key 2116. Individual converted selection codes comprising asecond group of converted selection codes 2115 may be combined by a datamanipulator 2144 to form one or more strings of characters comprising aserver pre-key 2116. In some embodiments, individual converted selectioncodes may be combined through concatenation of units. Concatenation maycomprise using each of the individual converted selection codes as aunit or may comprise using pieces of each individual converted selectioncode as a unit. A server pre-key 2116 may be converted 2112 by a dataconverter 2145 to a server key 2105. In some embodiments, conversion2112 may comprise using hash algorithms. In other embodiments,conversion 2112 may comprise using encryption methods. Yet otherembodiments may comprise conversion 2112 using a combination of hashalgorithms and encryption methods.

According to some embodiments, a login key 2199 may be generated. Eachof a client key 2106 and a server key 2105 may be separated by a datamanipulator 2144 into a client key first part 2117, a client key secondpart 2118, a server key first part 2119, and a server key second part2120. A client key first part 2117 and a client key second part 2118 maycomprise different portions of the characters that comprise a client key2106. In a specific embodiment, each of a client key first part 2117 anda client key second part 2118 may be one half of a client key 2106. Aserver key first part 2119 and a server key second part 2120 maycomprise different portions of the characters that comprise a server key2105. In a specific embodiment, each of a server key first part 2119 anda server key second part 2120 may be one half of a server key 2105. Aclient key first part 2117, a client key second part 2118, a server keyfirst part 2119, and a server key second part 2120 may be combined by adata manipulator 2144 through concatenation of units to form one or morestrings of characters comprising a first pre-key 2121. Concatenation maycomprise using each of a client key first part 2117, a client key secondpart 2118, a server key first part 2119, and a server key second part2120 as a unit or may comprise using pieces of a client key first part2117, a client key second part 2118, a server key first part 2119, and aserver key second part 2120 as a unit.

A first pre-key 2121 may be converted 2112 by a data converter 2145 intoa one or more strings of characters comprising a second pre-key 2122. Insome embodiments, conversion 2112 may comprise using hash algorithms. Inother embodiments, conversion 2112 may comprise using encryptionmethods. Yet other embodiments may comprise conversion 2112 using acombination of hash algorithms and encryption methods. A second pre-key2122 may be used to generate a registration pre-key 2123. According tosome embodiments, a second pre-key 2122 and a client registration code2103 may be concatenated by a data manipulator 2144 to form one or morestrings of characters comprising a registration pre-key 2123.Concatenation may comprise using each of a second pre-key 2122 and aclient registration code 2103 as a unit or may comprise using pieces ofa second pre-key 2122 and a client registration code 2103 as a unit. Aclient registration code 2103 may be stored in a memory 2108 of a firstpeer 2101 by a processing migrator 2142 during a registration process. Aregistration pre-key 2123 may be converted 2112 by a data converter 2144into a one or more strings of characters comprising a registration key2107. In some embodiments, conversion 2112 may comprise using hashalgorithms. In other embodiments, conversion 2112 may comprise usingencryption methods. Yet other embodiments may comprise conversion 2112using a combination of hash algorithms and encryption methods. In someembodiments, a registration key 2107 may be identical to a registrationkey 1707 generated by a first peer 1701 during a registration method1700, shown in FIG. 17. Referring back to FIG. 21, a registration key2107 may be used to generate a login key 2199. In some embodiments, aregistration key 2107 and a login salt 2124 are used to generate a loginkey 2199. A registration key 2107 and a login salt 2024 may beconcatenated by a data manipulator 2144 to form one or more strings ofcharacters comprising a login pre-key 2198. Concatenation may compriseusing each of a registration key 2107 and a login salt 2024 as a unit ormay comprise using pieces of a registration key 2107 and a login salt2024 as a unit. A login pre-key 2198 may be used to generate a login key2199. In some embodiments, a login pre-key 2198 may be converted 2112 bya data converter 2145 to a login key 2199. In some embodiments,conversion 2112 may comprise using hash algorithms. In otherembodiments, conversion 2112 may comprise using encryption methods. Yetother embodiments may comprise conversion 2112 using a combination ofhash algorithms and encryption methods.

A first peer 2101 may transmit information to a server 2150. Accordingto some embodiments, a transmitter/receiver 2141 of a first peer 2101may transmit a login key 2199 and a server key 2105 to a server 2150. Inother embodiments, a transmitter/receiver 2141 of a first peer 2101 maytransmit a login key 2199, a server key 2105, and other informationnecessary for a login method to a server 2150.

A login method may further comprise distributing one or moreverification keys. Illustrated in FIG. 22, a server 2250 may receiveinformation from a first peer 2201. According to some embodiments, atransmitter/receiver 2241 of a server 2250 may receive a login key 2299from a first peer 2201. A transmitter/receiver 2241 of a server 2250 mayreceive a server key 2205 from a first peer 2201. A transmitter/receiver2241 of a server 2250 may receive both a login key 2299 and a server key2205 from a first peer 2201. In some embodiments, a server 2250 maygenerate a comparison login key 2260. A comparison login key 2260 may begenerated using a registration key 2207 that has been stored in adatabase 2257 of a server 2250 during a registration method. Aprocessing migrator 2242 of a server 2250 may migrate a registration key2207 and a login salt 2224 from a database 2257. A data manipulator 2244of a server 2250 may combine a registration key 2207 and a login salt2224 by concatenation to generate a comparison login pre-key. Acomparison login pre-key may be converted 2212 by a data converter 2245to a comparison login key 2260. In some embodiments, conversion 2212 maycomprise using hash algorithms. In other embodiments, conversion 2212may comprise using encryption methods. Yet other embodiments maycomprise conversion 2212 using a combination of hash algorithms andencryption methods. A processing verifier 2247 of a server 2250 maycompare a comparison login key 2260 to a login key 2299 sent by a firstpeer 2201 to determine if a first peer 2201 may be communicated with.

A login key 2299 may be stored in a database 2257 of a server 2250 by aprocessing migrator 2242. A server may access a previously stored peerlist 2258 using a data migrator 2242. A stored peer list 2258 maycomprise a list of peer devices, e.g. a first peer 2201, a second peer2275, on the network. A peer list may also comprise recipient codes 2252and distribution codes 2256, which may comprise a one or more strings ofcharacters of any length. Additionally, a processing generator 2246 of aserver 2250 may generate a sender code 2254, which may also comprise aone or more strings of characters of any length.

A data manipulator 2244 of a server 2250 may generate a distributionpre-key 2259 by combining any combination of a server key 2205, arecipient code 2252, a sender code 2254, a distribution code 2256, or alogin key 2299. In some embodiments, a distribution pre-key 2259 iscomprised of a server key 2205, a sender code 2254, and a recipient code2252, which may be combined through concatenation of units to form oneor more strings of characters. Concatenation may comprise using each ofa server key 2205, a sender code 2254, and a recipient code 2252 as aunit or may comprise using pieces of a server key 2205, a sender code2254, and a recipient code 2252 as a unit. A distribution pre-key 2259may be converted 2212 by a data converter 2245 into a one or morestrings of characters comprising a distribution key 2253. In someembodiments, conversion 2212 may comprise using hash algorithms. Inother embodiments, conversion 2212 may comprise using encryptionmethods. Yet other embodiments may comprise conversion 2212 using acombination of hash algorithms and encryption methods. A distributionkey 2253 may be stored in a database 2257 of a server 2250. Averification pre-key 2261 may be generated by a data manipulator 2244 ofa server 2250. In some embodiments, a distribution key 2253 and averification salt 2263, generated by a processing generator 2246 of aserver 2250 and comprising any number of characters, may be concatenatedto generate a verification pre-key 2261. A verification pre-key 2261 maybe converted 2212 by a data converter 2245 into a verification key 2262.In some embodiments, conversion 2212 may comprise using hash algorithms.In other embodiments, conversion 2212 may comprise using encryptionmethods. Yet other embodiments may comprise conversion 2212 using acombination of hash algorithms and encryption methods.

A server 2250 may be configured to transmit information to a second peer2275. In some embodiments, a transmitter/receiver 2241 of a server 2250may transmit a verification key 2262 and a distribution code 2256 to asecond peer 2275. In other embodiments, a transmitter/receiver 2241 of aserver 2250 may transmit a verification key 2262, a distribution code2256, a verification salt 2263, and other information necessary for alogin method 2000 to a second peer 2275. In some embodiments, a server2250 may transmit any combination of a distribution key 2253, averification salt 2263, and a distribution code 2256 to a second peer2275.

A server 2250 may generate more than one verification keys 2262 andtransmit data to more than one second peer 2275. In some embodiments, apeer list 2258 may comprise a list of more than one second peers 2275 onthe network. A second peer may comprise any IoT device, server, or anydevice that is on a network and capable of transmitting and receivingdata from a server 2250. A server 2250 may generate a uniquedistribution code 2256 for each second peer 2275. A server 2250 maygenerate a unique recipient code 2252 for each second peer 2275. Inthese embodiments, a verification key 2262 created for each second peer2275 may be different from verification keys 2262 created for othersecond peers 2275, although underlying server keys 2205 received from afirst peer 2201 may be identical. Verification keys 2262 may or may notbe stored at a database 2257 of a server 2250.

Referring now to FIG. 23, a login method may comprise verifying one ormore login keys on a local database. According to some embodiments, asecond peer 2375 may be configured to receive and transmit informationto a server 2350. A transmitter/receiver 2341 of a second peer 2375 mayreceive a verification key 2362 from a server 2350. Atransmitter/receiver 2341 of a second peer 2375 may receive adistribution code 2356 from a server 2350. In some embodiments, atransmitter/receiver 2341 of a second peer 2375 may receive averification key 2362, a distribution code 2356, and verification salt2363 from a server 2350. A distribution code 2356 may be compared by aprocessing verifier 2347 across all distribution codes 2356 stored in amemory 2378 of a second peer 2375. If a distribution code 2356 receivedfrom a server 2350 is identical to a distribution code 2356 stored in amemory 2378 of a second peer 2375, then a processing generator 2346 of asecond peer 2375 may produce a result 2382 that is affirmative. If adistribution code 2356 received by a second peer 2375 is not identicalto a distribution code 2356 stored in a memory 2378 of a second peer2375, then a processing generator 2346 of a second peer 2375 may producea result 2382 that is negative. In some embodiments, a verification key2362 is also used to locate identical distribution codes 2356. If asecond peer 2375 determines that one or more distribution codes 2356stored in a memory 2378 of a second peer 2375 is identical to adistribution code 2356 received from a server 2350, then a processingmigrator 2342 of a second peer 2375 may remove a distribution key 2353that is associated with a matching distribution code 2356 from a memory2378. A distribution key 2353 removed from a memory 2378 of a secondpeer 2375 and a verification salt 2363 may be used by a data manipulator2344 to generate a confirmation pre-key 2380 by concatenation. Aconfirmation pre-key 2380 may be converted 2312 by a data converter 2345to a confirmation key 2381. In some embodiments, conversion 2312 maycomprise using hash algorithms. In other embodiments, conversion 2312may comprise using encryption methods. Yet other embodiments maycomprise conversion 2312 using a combination of hash algorithms andencryption methods.

In some embodiments, a second peer 2375 may receive a distribution keyand a verification salt 2363 from a server 2350. A second peer 2375 maygenerate a verification key 2362 at a second peer 2375 by concatenationof a distribution key and a verification salt 2363 to generate averification pre-key. A verification pre-key may be converted 2312 to averification kay 2362.

In some embodiments, a second peer 2375 may generate a comparisonverification key 2383. A second peer 2375 may generate a comparisonverification key 2383 by concatenation of a stored distribution key 2353and a verification salt 2363 received from a server 2350 to generate acomparison verification pre-key. A comparison verification pre-key maybe converted 2312 to a comparison verification key. In some embodiments,a comparison verification key 2383 may be compared by a processingverifier 2347 to a received verification key 2362 and a result 2382 maybe generated. In some embodiments, a result 2382 may comprise a resultgenerated from comparing a verification key 2362 to a comparisonverification key 2383 and a result generated from comparing a receiveddistribution code 2356 to a stored distribution code 2356. Aconfirmation key 2381 may be generated from a verification salt 2363 anda deposit key 2377 retrieved from a memory 2378 of a second peer 2375. Adeposit key 2377 and a verification salt 2363 may be concatenated by adata manipulator 2344 to generate a confirmation pre-key 2380. Aconfirmation pre-key 2380 may be converted 2312 to a confirmation key2381. Any combination of a confirmation key 2381, a distribution code2356, and a result 2382 may be transmitted from a second peer 2375 to aserver 2350.

A second peer 2375 may be configured to transmit data to a server 2350.In some embodiments, a transmitter/receiver 2341 of a second peer 2375may transmit any combination of a result 2382, a distribution code 2356,and a confirmation key 2381 to a server 2350. In some embodiments, asecond peer 2375 may be configured to delete all data associated with atransaction. In a specific embodiment, a second peer 2375 may delete anycombination of a distribution code 2356, a deposit key 2377, adistribution key 2353, a verification key 2362, a verification salt2326, a confirmation pre-key 2380, and a confirmation key 2381 from amemory 2378 of a second peer 2375 or from a processor of a second peer2375. In some embodiments, deletion of data may occur contemporaneouslywith transmitting data to a server 2350. In other embodiments, deletionof data may occur after transmitting data to a server 2350.

Referring now to FIG. 24, a login method may further comprise validatinga verification process 2400. A server 2450 may be configured to receivedata from a one or more second peers 2475. In some embodiments, atransmitter/receiver 2441 of a server 2450 may receive any combinationof a confirmation key 2481, a result 2482, and a distribution code 2456.A server 2450 may acknowledge a result 2482 received from a second peer2475. In the event that a result is affirmative, a processing verifier2447 of a server 2450 may compare a distribution code 2456 received froma second peer 2475 to all or some distribution codes 2456 stored in adatabase 2457 of a server 2450. If a distribution code 2456 stored in adatabase 2457 of a server 2450 is identical to a distribution code 2456received from a second peer 2475, then a processing migrator 2442 of aserver 2450 may retrieve any combination of a verification salt 2463 anda distribution key 2453 which may be associated with a distribution code2456 and stored in a database 2457 of a server 2450. In someembodiments, a retrieved distribution key 2453 may be a distribution key2453 which was stored during a registration process. A retrievedverification salt 2463 and a retrieved distribution key 2453 may be usedby a data manipulator 2444 to generate a verification pre-key 2461through concatenation of a verification salt 2463 and a distribution key2453. A verification pre-key 2461 may be converted 2412 by a dataconverter 2445 to a verification key 2462. In some embodiments,conversion 2412 may comprise using hash algorithms. In otherembodiments, conversion 2412 may comprise using encryption methods. Yetother embodiments may comprise conversion 2412 using a combination ofhash algorithms and encryption methods.

A processing verifier 2447 of a server 2450 may compare a generatedverification key 2462 to a confirmation key 2481 received from a secondpeer 2475 and a processing generator 2246 may produce an authenticationresult 2464. If a verification key 2462 is identical to a confirmationkey 2481 received from a second peer 2475, a result might beaffirmative, e.g. authentication success. If a verification key 2462 isnot identical to a confirmation key 2481 received from a second peer2475, then an authentication result 2464 may be negative, e.g.authentication failure or threat. A processing migrator 2442 of a server2450 may store an authentication result 2464 in a database 2457. In someembodiments, an authentication result 2464 is stored with an associateddistribution key 2453 generated during a registration method.

A server 2450 may send new distribution keys 2453 to one or more secondpeers 2475. Referring now to FIG. 19, a server 1950 may generate a newpeer list 1958 in a database 1957 of a server 1950. In some embodiments,a server 1950 may assign any combination of a new recipient code 1952and a new distribution code 1956 and use any combination of a newrecipient code 1952 and a new distribution code 1956 to generate a newdistribution key 1953, in a method which may be identical todistributing one or more distribution keys 1900. A server 1950 maytransmit newly generated distribution keys 1953 to second peers 1975which may be different from second peers 1975 which previously storeddistribution keys 1953.

A web authentication method may comprise generating a bar code,generating one or more keys, and establishing a web session. Further, aweb authentication system may comprise communication between one or morefirst devices, second devices, first servers, second servers, andinternet applications. One or more first devices, second devices, firstservers, and second servers may comprise at least a processor and atransmitter/receiver. One or more first devices and one or more seconddevices may additionally comprise a respective memory. In someembodiments, each of one or more first devices and one or second devicesmay comprise a visual display. Each of one or more first devices and oneor second devices may comprise a means to scan a bar code. One or morefirst servers and second servers may additionally comprise a database.

A transmitter of a first device, a second device, a first server, and asecond server may be configured to transmit and receive information froman exogenous source. In some embodiments, a first device may beconfigured to transmit and receive information from any combination of asecond device, a first server, and a second server. A first server and asecond server may be configured to transmit and receive information fromboth a first device and a second device, and a second device may beconfigured to transmit and receive information from a first server, afirst device, and a second server. A memory of a first device and asecond device and a database of a server may be configured to storeinformation and to allow information to be retrieved. A visual displaymay additionally comprise a means for a user to interact with a display,e.g. enter data, select characters, select objects, etc. An internetapplication may be configured to transmit or receive information fromany combination of a first server, a second server, a first device, anda second device.

A processor of a first device, a second device, a first server, and asecond server may comprise a processing migrator, a data manipulator, adata converter, a processing generator, and a processing verifier. Aprocessing migrator may be configured to migrate data from one componentwithin a first device, a second device, or first or second server toanother component within a first device, a second device, or a first orsecond server. By way of example, and not limitation, a processingmigrator may be configured to move data from a memory of a first deviceto a processor of a first device, or from a processor of a second deviceto a transmitter/receiver of a second device. A data manipulator may beconfigured to manipulate data, e.g. combine, separate, separate andrecombine, reorder, etc. By way of example, and not limitation, a datamanipulator of a first device may be configured to separate a one ormore strings of characters into a first portion and a second portion, ora data manipulator of a server may be configured to combine a firstportion of data with a second portion of data to produce one or morestrings of characters.

A data converter may be configured to convert a first string ofcharacters into a second string of characters, wherein each of a firststring of characters and a second string of characters may be differentin any one or more of length, composition, or arrangement. In someembodiments, a data converter may be configured to apply hash algorithmsto a first string of characters. In other embodiments, a data convertermay be configured to apply encryption protocols to a first string ofcharacters. In yet other embodiments, a data converter may be configuredto apply decryption protocols to a first string of characters. In otherembodiments still, a data converter may be configured to apply anycombination of hash algorithms, encryption protocols, decryptionprotocols, or any other known method of data conversion to a firststring of characters to produce a second string of characters.

A processing generator may be configured to produce data. In someembodiments, data may comprise a one or more strings of characters ofany length and may comprise bar codes and the like. In some embodiments,data may be produced in a random manner or a directed manner. Aprocessing verifier may be configured to compare two or more data anddetermine if those data are identical or different. In some embodiments,a processing verifier and a processing generator may be paired todetermine if a first string of characters and a second string ofcharacters are identical and generate a response based on the identityof a first and second string of characters.

A web authentication method may comprise generating a bar code,illustrated in FIG. 25. Generating a bar code 2500 may be initiated atan internet application 2590. In some embodiments, a user may initiategenerating a bar code 2500 at an internet application 2590 with a loginrequest. A first agreement protocol pair 2646 may be generated by aprocessing generator 2646. In some embodiments, a first agreementprotocol pair 2646 may be generated by a processing generator 2646 at aninternet application 2590. A first key agreement protocol pair 2526 maycomprise any key agreement protocol pair that is readily known to aperson having ordinary skill in the art. In some embodiments, a firstkey agreement protocol pair 2526 may comprise an Elliptic-curveDiffie-Hellman (ECDH) pair. According to some embodiments, an internetapplication 2590 may be configured to transmit information to a firstserver 2525. A processing migrator 2642 may transfer information to atransmitter/receiver 2541 of an internet application 2590. An internetapplication 2590 may transmit any combination of a first public key2503, a first private key 2504, and any other information necessary togenerate a bar code 2505.

In some embodiments, a first server 2525 may be configured to receiveinformation from an internet application 2590. A transmitter/receiver2541 of a first server 2525 may receive any combination of a firstpublic key 2503, a first private key 2504, and any other necessaryinformation for generating a bar code 2500 from an internet application2590. A first server 2525 may generate a random key 2527 and a randomkey 2527 may be generated by a processing generator 2646 of a firstserver 2525. A random key 2527 may comprise one or more strings ofcharacters of any length and characters may comprise letters, numbers,and symbols. In some embodiments, a bar code 2505 may be generated. Aprocessing generator 2546 may use a bar code precursor to generate a barcode 2505. A bar code 2505 may comprise any type of barcode 2505,including without limitation any linear barcode, 2-dimensional bar code,or any type of readable indicia readily known to a person havingordinary skill in the art. In some embodiments, a bar code 2505 maycomprise a QR code. A bar code 2505 may be generated from anycombination of a first public key 2503, a first private key 2504, arandom key 2527, and any other information necessary for generating abar code 2500. In a specific embodiment, a bar code 2505 may begenerated by a data manipulator 2544 of a first server 2525 and may bebased on a first public key 2503 and a random key 2527. A first server2525 may be configured to transfer information to an internetapplication 2590. In some embodiments, a transmitter/receiver 2541 of afirst server 2525 may transmit information to an internet application2590. In a specific embodiment, a first server 2525 may transmit a barcode 2505 to an internet application 2590. An internet application 2590may receive a bar code 2505 at a transmitter/receiver 2541 and maydisplay a bar code 2505 at a visual display 2590 of an internetapplication 2590.

A web authentication method may comprise generating one or more keys,illustrated in FIGS. 26, 27, and 28. Referring now to FIG. 26,generating one or more keys 2600 may comprise a first device 2650scanning a bar code 2605. A data manipulator 2644 of a first device 2650may generate a random key 2627, a first public key 2603, or a random key2627 and a first public key 2603 from information contained within a barcode 2605. A data manipulator 2644 may extrapolate any informationcontained within a bar code 2605 for the purpose of generating one ormore keys 2600. Further, a processing generator 2646 of a first device2650 may generate a second key agreement protocol pair 2651. A secondkey agreement protocol pair 2651 may comprise any key agreement protocolpair that is readily known to a person having ordinary skill in the art.In some embodiments, a second key agreement protocol pair 2651 maycomprise an Elliptic-curve Diffie-Hellman (ECDH) pair. In someembodiments, a second key agreement protocol pair 2651 may comprise asecond private key 2652 and a second public key 2653. A second privatekey 2652 and a first public key 2603 extrapolated from a bar code 2605may be combined by a data manipulator 2644 to generate a secret key2654. A processing generator 2646 of a first device 2650 may generateany combination of a salt 2655, an initializing vector 2656, and aniteration number 2657. In a specific embodiment, a processing generator2646 of a first device 2650 may generate each of a salt 2655, aninitializing vector 2656, and an iteration number 2657. A salt 2655, aninitializing vector 2656, and an iteration number 2657, may respectivelycomprise a one or more strings of characters of any length andcharacters may comprise any combination of letters, numbers, or symbols.An initializing vector 2656 may comprise a number of characters equal ton, and may additionally comprise an IV first part 2658 and an IV secondpart 2659. An IV first part 2658 and an IV second part 2659 may eachcomprise a number of characters between one and n−1. An iteration number2657 may comprise a number of characters equal to n, and additionallycomprise an IN first part 2660 and an IN second part 2661. An IN firstpart 2660 and an IN second part 2661 may each comprise a number ofcharacters between one and n−1. A data manipulator 2644 may produce anIV first part 2658 and an IV second part 2659 from an initializingvector 2656. A data manipulator 2644 may produce an IN first part 2660and an IN second part 2661 from an iteration number 2657. According tosome embodiments, a secret key 2654, a salt 2655, an IV first part 2658,and an IN first part 2660 may be converted 2612 by a data converter 2645to a masked secret key 2662, a masked salt 2663, a masked IV first part2664, and a masked IN first part 2665, respectively. In someembodiments, an initializing vector 2656 may be converted 2612 by a dataconverter 2645 to a masked IV first part 2664. Likewise, an iterationnumber 2657 may be converted 2612 by a data converter 2645 to a maskedIN first part 2665. In some embodiments, conversion 2612 may compriseusing hash algorithms. In other embodiments, conversion 2612 maycomprise using encryption methods. Yet other embodiments may compriseconversion 2612 using a combination of hash algorithms and encryptionmethods. In some embodiments, an iteration number 2657 may remainintact, not generating an IN first part 2660 and an IN second part 2661and a resulting IN first part 2660 may not be converted 2612.

A processing generator 2646 of a first device 2650 may generate a clientkey 2666. A client key 2666 may comprise a one or more strings ofcharacters of any length and characters may comprise any combination ofletters, numbers, or symbols. According to some embodiments, a clientkey 2666 may be converted 2612 by a data converter 2645 to a firstmasked client key 2667. In other embodiments, a client key 2667 may beconverted 2612 by a data converter 2645 to a second masked client key2668. In yet other embodiments, a client key 2666 may be converted 2612by a data converter 2645 into each of a first masked client key 2667 anda second masked client key 2668. Conversion 2612 may comprise using hashalgorithms. Additionally, conversion 2612 may comprise using encryptionmethods. In some embodiments, conversion 2612 may comprise a combinationof hash algorithms and encryption methods. A first device 2650 may beconfigured to transmit information to a first server 2625. In someembodiments, a transmitter/receiver 2641 of a first device 2650 maytransmit any combination of a first masked client key 2667, a secondmasked client key 2668, a masked secret key 2662, a masked salt 2663, amasked IV first part 2664, and a masked IN first part 2665 to a firstserver 2625. In some embodiments, a first device 2650 may display eachof an IV second part 2659 and an IN second part 2661 on a visual display2669 of a first device 2650. In a specific embodiment, an iterationnumber 2657 may be displayed in its entirety on a visual display 2669 ofa first device 2650.

Referring now to FIG. 27, generating one or more keys may comprise afirst server 2725 receiving information from a first device 2750. Insome embodiments, a transmitter/receiver 2741 of a first server 2725 mayreceive any combination of a masked secret key 2762, a second maskedclient key 2768, a masked salt 2763, a masked IV first part 2764, amasked IN first part 2765, and a first masked client key 2767 from afirst device 2750. In some embodiments, a processing migrator 2742 of afirst server 2725 may store one or more of a masked secret key 2762, asecond masked client key 2768, a masked salt 2763, a masked IV firstpart 2764, a masked IN first part 2765, and a first masked client key2767 received from a first device 2750 in a database 2729 of a firstserver 2725. According to a specific embodiment, a processing migrator2742 of a first server 2725 may store a first masked client key 2767 ina database 2729 of a first server 2729.

A first server 2725 may be configured to transmit information to aninternet application 2790. In some embodiments, a transmitter/receiver2741 of a first server 2725 may transmit any combination of a maskedsecret key 2762, a second masked client key 2768, a masked salt 2763, amasked IV first part 2764, a masked IN first part 2765, and a firstmasked client key 2767 to a first server 2725. In a specific embodiment,a transmitter/receiver 2741 of a first server 2725 may transmit a maskedsecret key 2762, a second masked client key 2768, a masked salt 2763, amasked IV first part 2764, and a masked IN first part 2765 to a firstserver 2725. In other embodiments, a transmitter/receiver 2741 of afirst server 2725 may transmit any combination of a masked secret key2762, a second masked client key 2768, a masked salt 2763, and a maskedIV first part 2764 to an internet application 2790 (collectivelyreferred to as “received data 2728” from this point forward).

Illustrated in FIG. 28, generating one or more keys 2800 may comprise atransmitter/receiver 2841 of an internet application 2890 receivingreceived data 2828 from a first server 2825. A first device 2850 maycontain user input 2869, which may comprise an IV second part 2659 andan IN second part 2661 (see FIG. 26), which may respectively comprisestrings of characters. User input 2869 may comprise an IV first part andan iteration number. In some embodiments, user input 2869 may bedisplayed on a graphical display 2869 of a first device 2850. Generatingone or more keys may comprise user input 2869 being entered into aninternet application 2890. A data converter 2844 of an internetapplication 2890 may convert 2812 received data 2828 into one or more ofa secret key 2854, an IN first part 2860, a salt 2855, an IV first part2858, and a client key 2866. Conversion 2812 may comprise using hashalgorithms. Additionally, conversion 2812 may comprise using encryptionmethods. Conversion may comprise using decryption methods. In someembodiments, conversion 2812 may comprise any combination of hashalgorithms, encryption methods, or decryption methods. According to someembodiments, a data converter 2844 of an internet application 2890 mayuse both user input 2869 and received data 2828 to convert 2812 receiveddata 2828 into one or more of a secret key 2854, an IN first part 2860,a salt 2855, an IV first part 2858, and a client key 2866. A processingmigrator 2842 may store a client key 2866 in a storage 2891 of aninternet application 2890. A data converter 2845 of an internetapplication 2890 may convert 2812 a client key 2866 into a third maskedclient key 2892. In some embodiments, a third masked client key 2892 maybe migrated by a processing migrator 2842 to a transmitter/receiver 2841of an internet application 2890. A transmitter/receiver 2841 of aninternet application 2890 may transmit a third masked client key 2892 toa first server 2825.

A web authentication method may comprise establishing a web session.Illustrated in FIG. 29, a transmitter/receiver 2941 of a first server2825 may receive a third masked client key 2992 from an internetapplication 2990. According to some embodiments, a processing migrator2942 of a first server 2825 may retrieve a stored first masked clientkey 2967 from a database 2929 of a first server 2825. A processingverifier 2947 may compare a retrieved first masked client key 2967 to athird masked client key 2992 received from an internet application 2990.A processing generator 2946 may generate a result 2930 based on theidentity of a first masked client key 2967 and a third masked client key2992. A transmitter/receiver 2941 of a first server 2825 may transmit aresult 2930 to a second server 2980. A transmitter/receiver 2941 of asecond server 2980 may receive a result 2930 from a first server 2825and generate a web token 2931. A web token 2931 may be generated by aprocessing generator 2946. In some embodiments, a web token 2931 may beany means known in the art for authorizing the establishment of a websession. A second server 2980 may transmit a generated web token 2931 tofirst server 2825. A transmitter/receiver 2941 of a first server 2825may receive a web token 2931 from a second server 2980 and may transmita received web token 2931 to an internet application 2990. Atransmitter/receiver 2941 of an internet application 2990 may receive aweb token 2931 from a first server 2825.

In some embodiments, an internet application may transmit a received webtoken to a second server. A second server may receive a web token from aweb browser and may establish a web session. Further, a second servermay be configured to transmit information to a first server. In someembodiments, a second server may transmit information regarding receiptof a web token from an internet application. Information regardingreceipt of a web token from an internet application may comprise withoutlimitation any information about the internet application, informationabout a user of an internet application, information about access to aweb session, spatial and/or temporal information about any component ofa system described herein. A first server may receive informationregarding receipt of a web token from a second server. In someembodiments, a first server may be configured to transmit information toa first device, including without limitation, information regardingreceipt of a web token.

Generating Keys to Protect Sensitive Data

It will be appreciated that any method, system, component, and/orembodiment disclosed appearing in any part of this disclosure may becombined with any other method, system, component and/or embodimentappearing in any other part of this disclosure. Biometrics may beincorporated into any embodiments described herein as codes,information, data, etc.

In some embodiments, keys (e.g., privacy keys) may be generated in orderto protect the contents of sensitive data transmissions. For example,where a first data comprises sensitive information such as biometricdata, sensitive communications, etc., using controlled corruption togenerate keys may provide an elegant means by which the sensitive data(e.g., first data), may be protected against a third-party interception.Sensitive data (e.g., first data) may comprise any number of data types,for example and without limitation, biometric data, documents, textmessages, email messages, or other types of sensitive communications.

According to some embodiments, systems and methods of generating keys(e.g., privacy keys) using controlled corruption may include one or morecomputing devices (e.g., first computing device, second computingdevice, third computing device, etc.) and one or more servers. The oneor more servers may comprise security engine, an action engine, and oneor more libraries. In some embodiments, one or more servers may furthercomprise a client layer comprising the one or more computing device(e.g., first computing device, second computing device, etc.) maycomprise a mobile platform and one or more libraries. A computing device(e.g., first computing device, second computing device, etc.) may be anyserver or any IoT device, i.e. any device that may connect to a networkand have the ability to transmit data, including but not limited to cellphones, personal assistants, buttons, home security systems, appliances,and the like.

FIG. 30 is an example system, according to a specific embodiment, forgenerating keys using controlled corruption 3000. The system may includea web layer 3010 comprising a first computing device 3012, anadministrative layer 3020 comprising one or more servers 3022, and aclient layer 3030 comprising one or more servers 3022. A system 3000 mayadditionally include one or more communications channels (e.g., internetgateways and one or more virtual private network (VPN) tunnels), shownin dotted lines.

The web layer 3010 may further comprise an administrative mobileplatform (AMP) 3014 comprising an administrative mobile library (AML)and a partner mobile library (PML) and an administrative web platform(AWP) 3016 comprising an administrative web library (AWL) and a partnerweb library (PWL). As used herein, any library may mean, withoutlimitation, any application, application database, database, and/ordata.

The administrative layer 3020 may further comprise an administrativesecurity engine (ASE), 3024 an action engine (AE) 3026, anadministrative partner library (APL) 3028, and one or more nodes 3029associated with the administrative layer. The one or more nodes 3029 maycomprise one or more databases, one or more user devices (e.g.,computing devices), or any combination of one or more databases and oneor more user devices (e.g., computing devices).

The client layer 3030 may additionally comprise an administrative clientlibrary (ACL) 3034 and a client server application (CSA) 3036. In someembodiments, the client layer 3030 and the administrative layer 3020 maybe in communication with one another using a VPN tunnel.

FIG. 31 is an example server-side (e.g., comprised in the administrativelayer 3020) method of generating keys using controlled corruption 3100,according to a specific embodiment, which may comprise registering afirst computing device at one or more servers 3140; receiving, at theone or more servers, a first privacy code and one or more parametersassociated with first data from the first computing device 3142;generating, at the one or more servers, a chunk count and a public key3143; transmitting the chunk count and public key to the first computingdevice 3144; receiving, at the one or more servers, a quantity of firstprivacy keys and a second privacy code 3146; and generating, at the oneor more servers, second data based on the privacy keys 3148.

Registering a computing device (e.g., first computing device) 3140 maycomprise installing one or more applications on the computing device,where the one or more applications may comprise a mobile platform andone or more libraries. In some embodiments, the computing device and oneor more applications may comprise a web layer of a system for generatingprivacy keys. A computing device may be in communication (e.g., networkcommunication, internet communication, virtual private network (VPNcommunication)) with one or more servers which may comprise anadministrative layer. A detailed discussion of different methods ofcommunication may be found in the preceding sections of thisspecification. According to some embodiments, registration of acomputing device comprised in the web layer may include initiatingcommunications and transmission of information between theadministrative layer (e.g., an ASE), the client layer (e.g., a CSA), andthe web layer (e.g., an AML and/or AWL comprised in a computing device).

One or more servers comprised in an administrative layer may receive,from a computing device (e.g., first computing device) a first privacycode and one or more parameters associated with first data 3142. Asdiscussed above, first data may comprise any data (e.g., biometric data,documents, messages, etc.) which a user may desire to protect intransmission. One or more parameters associated with first data mayinclude any information about the first data, including withoutlimitation, device identifiers, camera identifiers, file size, dataformat, application identifiers, user identifiers, personal identifiers,metadata, etc. In some embodiments, one or more parameters associatedwith the first data may include a file size, a public key associatedwith an asymmetric cryptographic key pair (which may identify the originof the first data), and a manipulated version of the first data (e.g., acompressed or “zipped” version of the data). In some embodiments,parameters associated with a first data may include a base 64 version ofa compressed (e.g., zipped) first data. A privacy code may comprise astring of alphanumeric and/or symbolic characters associated with a userof the computing device or with the origin of the first data. In aspecific embodiment, a privacy code is a first user input comprising apersonal identification number (e.g., PIN) selected by a user of thecomputing device. A privacy code may be based on user input, forexample, an encrypted version, a hashed version, a truncated version, ora rearranged version of a user input. In some embodiments, a privacycode may be generated automatically by a component of the system (e.g.,server, first computing device, etc.). In some embodiments, a privacycode may comprise and/or may be based on a digital footprint of a user.In these embodiments, a user's digital footprint may compriseinformation about a user's digital habits including, but not limited to,browsing history, browsing times/duration/frequency, usage habits,application usage, purchasing habits, geolocation data, etc.

One or more servers comprised in an administrative layer may generate achunk count, chunk names, and a public key associated with an APL 3143.The chunk count and chunk names may be based, at least in part, on thereceived parameters associated with a first data. A chunk count,according to some embodiments, may be an integer that informs adownstream process of generating privacy keys. Chunk names may bealphanumeric and/or symbolic identifiers which may be associated withone or more privacy keys generated in a downstream process. In someembodiments, a chunk count is generated based on parameters associatedwith a first data, for example, one or more of the size of the firstdata, the size of a compressed first data, or the size of a compressedfirst data that has been converted to a base 64 file. Chunk names may begenerated based on the chunk count. For example, where a chunk count isan integer equal to three, then three chunk names will be generated,each designed to be associated with a downstream privacy key. As anotherexample, where a generated chunk count is equal to seven, then sevenchunk names will also be generated. In a downstream step, seven privacykeys will be generated and each of the seven privacy keys will beassigned one of the chunk names. A public key may be associated with anasymmetric cryptographic key pair associated with an APL comprised inthe administrative layer. A chunk count, chunk names, and public key maybe transmitted from one or more servers comprised in an administrativelayer to a computing device comprised in the web layer.

According to some embodiments, a quantity of privacy keys (based on oneor more of the first data, the chunk count, the chunk names, and theprivacy code) may be generated by a computing device comprised in theweb layer of a system for generating privacy keys. FIG. 32 is acomputing device-side illustration of a method of generating privacykeys 3200 according to come embodiments.

A computing device 3212 (e.g., a first computing device) comprised inthe web layer of the system may receive a chunk count 3260, chunk names3261, and a public key 3262 from one or more servers comprised in theadministrative layer of the system. As discussed above, a first data3263 may comprise any data that a user may consider secure and desire toprotect in transit. In some embodiments, a computing device 3212 maycondense (e.g., zip) a first data 3263 to generate a compressed firstdata 3264. A computing device 3212 may generate a base 64 of thecompressed first data 3265 where the base 64 of the compressed firstdata 3265 comprises a base 64 version of the compressed first data 3264.Using controlled corruption (e.g., a controlled file corruption), acomputing device 3212 may generate a first pre-key 3267 by adding acorruptor (e.g., first corruptor 3266) to the base 64 of the compressedfirst data 3265. As discussed above, a corruptor 3266 may comprise astring of alphanumeric and/or symbolic characters. In a specificembodiment, a first corruptor 3266 may be based on a formula. Forexample, a first corruptor 3266 may be generated by a computing device3212 by summing the first 30 characters comprised in the base 64 of thecompressed first data 3265. In another specific embodiment, a firstcorruptor 3266 may be generated by summing the first and thirdcharacters the comprised in the base 64 of the compressed first data3265, summing the second and fourth characters comprised in the base 64of the compressed first data 3265, summing the third and fifthcharacters comprised in the base 64 of the compressed first data 3265,etc., and concatenating the results to generate a string of numericcharacters which may then comprise a first corruptor 3266. Any number offormulas may be used to generate a corruptor (e.g., first corruptor3266, second corruptor 3268, third corruptor 3273, etc.) and thepossibilities are not limited to the examples above.

A computing device 3212 may generate a second pre-key 3269 by adding acorruptor (e.g., second corruptor 3268) to the first pre-key 3267. In aspecific embodiment, a corruptor (e.g., second corruptor 3268) maycomprise one or more alphanumeric and/or symbolic characters comprisedin a privacy code entered by a user. In some embodiments, a corruptor(e.g., second corruptor 3268) may comprise one or more alphanumericand/or symbolic characters comprised in a manipulated (e.g., hashed,encrypted, rearranged, truncated, etc.) privacy code entered by a user.In a specific embodiment, a second corruptor 3268 may be based on aformula.

A computing device 3212 may generate a salt 3270 and an initializingvector (IV) 3271. A detailed discussion of a salt 3270 and IV 3271 maybe found in earlier sections of this specification. A salt 3270 and IV3271 may be added to a second pre-key 3269 to generate a third pre-key3272. It should be appreciated that this addition (e.g., salt 3270 andIV 3271) is not always present when generating privacy keys and that,according to some embodiments, a second pre-key 3269 may be used togenerate chunks 3274 based on the chunk count 3260 without the additionof a salt 3270, IV 3271, or third corruptor 3273.

A third corruptor 3273 may be added to a third pre-key 3272. A thirdcorruptor 3273 may be generated by a computing device 3212 in any mannerdescribed above for a corruptor (e.g., first corruptor 3266, secondcorruptor 3268). In a specific embodiment, a third corruptor 3273 may bebased on a formula. In some embodiments, a third corruptor 3273 is addedto a third pre-key 3272 and the resulting string is then divided intochunks 3274 based on the chunk count 3260 received from theadministrative layer. As discussed above, a chunk count 3260 is aninteger that directs the number of chunks 3274 to be generated in amethod of generating keys 3200. For example, where the chunk count 3260is equal to three, then a computing device 3212 will divide the pre-key(e.g., third pre-key 3272, second pre-key 3269, third pre-key 3272 witha third corruptor 3273) into three chunks 3274.

In some embodiments, a third pre-key 3272 may be divided into chunks3274, which may then be used to generate privacy keys 3275 without usinga third corruptor 3273. In some embodiments, a third pre-key 3272 may bedivided into chunks 3274 and one or more third corruptors 3273 (or firstcorruptors, second corruptors, etc.) may be added to the chunks 3274 togenerate the privacy keys.

Chunks 3274 may be named according to chunk names 3261 to generateprivacy keys 3275. According to some embodiments, chunk names 3261 maybe generated at an administrative layer and received at a computingdevice 3212 comprised in the web layer. Chunk names 3261, as discussedabove, may be based at least in part on information received as part ofparameters associated with a first data (e.g., an initial package). In aspecific embodiment, the number of chunk names 3261 received is equal tothe chunk count 3260. For example, where a chunk count 3260 is equal tothree, three chunk names 3261 will be generated at the administrativelayer and received at a computing device 3212. Accordingly, in thisembodiment, three chunks 3274 will be generated (based on the chunkcount 3260) and each resulting chunk 3274 will have an associated chunkname 3261. In some embodiments, a chunk 3274 is associated with a singlechunk name 3261 to generate a privacy key 3275 comprising a chunk 3274with a chunk name 3261. Chunk names 3261, according to theseembodiments, are useful in downstream processes to organize privacy keys3275 to recreate the first data 3263 (e.g., a second data) on the serverside.

To illustrate the above, the following example is provided. Where athird pre-key 3272 comprises the string ‘123456789’ and a thirdcorruptor 3273 comprises the string ‘543’, a resulting string fromcontrolled corruption may comprise the string ‘123455436789’. If thechunk count 3260 is equal to three and the chunk names are ‘One’, ‘Two’,and ‘Three’, the resulting privacy keys may comprise the following:

Chunk Name Privacy Key String ‘One’  ‘123’ ‘Two’ ‘4554’ ‘Three’ ‘36789’ 

Chunk names 3261 may, according to some embodiments, facilitatedownstream ordering of the privacy keys 3275 to recreate the initialstring. Here, by ordering the privacy keys 3275 according to chunk names3261 (e.g., ‘One’, ‘Two’, ‘Three’), the initial string ‘123455436789’can be recreated on the server (e.g., administrative layer) side.

A computing device 3212 comprised in a web layer may transmit a quantity(equal to the chunk count 3260) of privacy keys 3275 to one or moreservers comprised in an administrative layer. A computing device 3212may generate a second privacy code 3277 based on the first privacy code3276. A second privacy code 3277, according to some embodiments, may bean alphanumeric and/or symbolic string of characters. A second privacycode 3277 may be a manipulated (e.g., compressed, hashed, encrypted,rearranged, truncated, etc.) first privacy code 3276. According to aspecific embodiment, a second privacy code 3277 is a hashed firstprivacy code 3276. A privacy code (e.g., first privacy code 3276, secondprivacy code 3277) may be transmitted from a computing device 3212comprised in the web layer of the system to one or more serverscomprised in an administrative layer of the system.

Referring now back to FIG. 31, a method of generating keys usingcontrolled corruption may comprise receiving a quantity of privacy keysand a second privacy code from a computing device 3146, and generatingsecond data based on the privacy keys 3148.

FIG. 33 illustrates a specific embodiment of generating second databased on the privacy keys 3300. A second data 3382, according to someembodiments, may comprise a reconstructed version of a first data. Forexample, a first data may originate at a computing device comprised in aweb layer of the system. The first data may be used to generate privacykeys 3375, which may be a corrupted version of the first data which maybe then transmitted in corrupted chunks (e.g., privacy keys) to one ormore servers comprised in the administrative layer. The privacy keys3375 may be concatenated and the corruptors (e.g., first corruptor 3366,second corruptor 3368, third corruptor 3373, etc.) removed in asystematic fashion such that the resulting second data 3382 is areconstructed version of the original first data.

One or more servers 3322 comprised in the administrative layer of thesystem may receive a quantity (e.g., one or more, two or more, three ormore) of privacy keys 3375 from a computing device comprised in the weblayer of the system. One or more servers 3322 may receive a secondprivacy code 3377 from a computing device. According to someembodiments, the one or more servers 3322 may concatenate the quantity(e.g., one or more, two or more, three or more) of privacy keys 3375 togenerate a concatenated key 3376. According to some embodiments, and asdiscussed above, chunk names 3361 may guide the process ofconcatenation, may determine the order in which the privacy keys 3375should be joined, or may direct the arrangement of the privacy keys 3375to generate a concatenated key 3376.

One or more servers 3322 may remove a third corruptor 3373 to generate afirst cleaned data 3377, remove a salt 3370 and IV 3371 to generate asecond cleaned data 3378, remove a second corruptor 3368 to generate athird cleaned data 3379, and remove a first corruptor 3366 to generate abase64 file of a compressed second data 3380. According to someembodiments, removal of corruptors may require recognition of thecorruptors (e.g., first corruptor 3366, second corruptor 3368, thirdcorruptor 3373, etc.) which need to be removed. In these embodiments,the one or more servers may use different recognition tools to recognizecorruptors. For example, where a corruptor has been generated at acomputing device using a privacy code (or a derivative of a privacy codesuch as a truncated privacy code), one or more servers may generate aprivacy code from a received second privacy code 3377. In a specificembodiment, a second privacy code 3377 is used to remove one or morecorruptors (e.g., first corruptor 3366, second corruptor 3368, thirdcorruptor 3373, etc.). In some embodiments, the one or more servers 3322use a formula to generate a corruptor (e.g., the same formula used togenerate a corruptor at the computing device) and use the newlygenerated corruptor to recognize a corruptor embedded in a cleaned data(e.g., first cleaned data 3377, second cleaned data 3378, third cleaneddata 3379, etc.) and remove it. Importantly, a characteristic of one ormore servers 3322 is the ability to recognize corruptors (e.g., firstcorruptor 3366, second corruptor 3368, third corruptor 3373, etc.) in aconcatenated key 3376 or in cleaned data (e.g., first cleaned data 3377,second cleaned data 3378, third cleaned data 3379, etc.) andsystematically remove them to generate a base 64 of a compressed seconddata 3380. In some embodiments, a concatenated key 3376 may be decryptedto generate a first cleaned data 3377.

A base 64 file of a compressed second data 3380 may be converted (e.g.,decoded) to a compressed second data 3381. According to someembodiments, a compressed second data 3381 may be converted (e.g.,unzipped) to a second data 3382. As discussed above, a second data 3382may be a reconstructed version of a first data. For example, where afirst data is information about a biometric scan, the second data willbe a reconstructed version of the original information about thebiometric scan. Where a first data is a sensitive email, text, or othercommunication, a second data is a reconstructed version of the sensitiveemail, text, or other communication. In this way, it will be appreciatedby one of ordinary skill in the art that any method or operationperformed by the one or more servers comprised in an administrativelayer may also be performed by a processor comprised in a secondcomputing device. For example, where the first data is a text messageoriginating from a mobile device comprising a first computing device,the second data (e.g., the reconstructed text message) may be generatedat a processor comprised in a second mobile device (e.g., a secondcomputing device).

Using Privacy Keys to Authenticate Identity

Privacy keys, according to some embodiments, may be used to authenticateidentity from a first computing device (e.g., a mobile computingdevice). In some embodiments, a first data may comprise a biometricscan, login password or code, or any other first data which may be basedon a user input. A method for generating privacy keys using controlledcorruption, and distributing, storing, and/or retrieving stored privacykeys to authenticate identity may include an enrollment module and asign in module.

Enrollment Module. An enrollment module may comprise methods to generatekeys (e.g., privacy keys) using controlled corruption and distribute andstore keys for later use. Using the methods and systems disclosedherein, privacy keys may be generated from the first data usingcontrolled corruption, transmitted to a server, and stored on multiplenodes associated with the server. When a user subsequently enters theiruser input (e.g., biometric scan, password, first data, third data,etc.) into a first computing device in a sign in module, the privacykeys generated by controlled corruption and based on the user input inthat module can be compared to privacy keys generated using a first datain the enrollment module and a user's identity can be authenticated. Bygenerating privacy keys using controlled corruption, a user's input,such as biometric data, may be protected.

FIG. 34 is an example server-side (e.g., comprised in the administrativelayer 3020) method of generating and distributing keys using controlledcorruption 3400, according to a specific embodiment, which may compriseregistering a first computing device at one or more servers 3440;receiving, at the one or more servers, a first privacy code and one ormore parameters associated with first data from the first computingdevice 3442; generating, at the one or more servers, a chunk count and apublic key 3443; transmitting the chunk count and public key to thefirst computing device 3444; receiving, at the one or more servers, aquantity of first privacy keys and a second privacy code 3446; andgenerating, at the one or more servers, second data based on the privacykeys 3448. According to some embodiments, privacy keys may be stored atone or more nodes associated with the one or more servers for lateruses, for example, authenticating identity. In these embodiments, amethod for generating and distributing keys 3400 may further comprisegenerating a result 3450, generating a receiver identifier and a privacycode identifier 3452, and distributing privacy keys, the receiveridentifier, and the privacy code identifier to one or more of the nodesassociated with the one or more servers 3454.

When privacy keys are generated for uses such as authentication, themethods of generating one or more privacy keys are generally the same asthose illustrated in FIGS. 31, 32, and 33 and discussed above. Inaddition to those methods, a method 3400 may include generating a result3450. According to some embodiments, a base 64 file of compressed seconddata (such as 3380 of FIG. 33) may be compared to a base 64 ofcompressed first data which may be received as a parameter associatedwith first data (such as in 3142 of FIG. 31). In these embodiments, thetwo base 64 files may be compared and a result may be generated 3450.Where the two base 64 files are identical, a result may be positive.Where the two base 64 files are not identical, a result may be negative.

In some embodiments, a result 3450 may be generated by comparing acompressed second data 3381 to a compressed first data. In someembodiments, a result 3450 may be generated by comparing a second data3382 to a first data. In some embodiments, a result may be generated bycomparing multiple elements (e.g., first and second data, compressedfirst and compressed second data, base64 of compressed first and base64of compressed second data, etc.). Iterative learning may be utilizedwhen generating a result 3450. For example, many second data 3382 may begenerated over time and these second data 3382 may be compared to oneanother, over time, to generate a result 3450. Although second data 3382is used as an example, a result 3450 may be generated by comparing anyof the elements (e.g., first data, compressed data, base64 compresseddata, privacy codes, etc.) over time.

In some embodiments, a positive result may prompt the one or moreservers comprised in an administrative layer to generate a receiveridentifier and a privacy code identifier 3452. A positive result mayprompt one or more servers comprised in an administrative layer togenerate two or more copies of each privacy key received from acomputing device 3446. The privacy keys, receiver identifier, andprivacy code identifier may be transmitted to one or more nodesassociated with the one or more servers for storage 3454. In someembodiments, the privacy keys, receiver identifier, and privacy codeidentifier may be manipulated before transmission.

Distributing privacy keys to one or more nodes for storage 3454 may bedone using a ledgerless non-descriptive distribution. This method ofdistribution may comprise using sender identifiers in conjunction withreceiver identifiers, privacy codes, and/or other user specific codes(e.g., biometrics, etc.) to generate unique piece descriptions for eachprivacy key. A sender identifier, according to some embodiments, may bea string of alphanumeric and/or symbolic characters used to identify anycombination of users, transactions, applications, and/or computingdevices. In these embodiments, a system may manipulate one or more ofprivacy keys, privacy codes, receiver identifiers, and senderidentifiers to generate a unique piece description for each privacy keydistributed. Piece descriptions, according to some embodiments, may becreated on an “as-needed” basis, eliminating the need for keepingledgers or other records of privacy keys destinations (e.g., nodes) atthe server.

Even if a hacker/virus is able to penetrate the defenses (e.g., firewalland other security features) and enter the system, not having anendpoint address (of where the data is distributed) stored in a centrallocation or a central ledger, ensures that the hacker will not knowwhere the nodes are or which nodes have a particular data.

Even if the nodes are compromised, this type of distribution ensuresthat the hacker will not be able to identify pieces that go together toform a data. This also provides protection against ransomware and hashigh fault tolerance. Furthermore, the manipulation (e.g., encryption,hashing, corruption, chunking, concatenation, etc.) process ensuresanother level of security, even if the pieces from the nodes areobtained, it cannot be put together in its original form without theauthorized user's consent.

The privacy keys, receiver identifier, and privacy code identifier maybe stored for later uses, including identity authentication in the signin module.

Sign In Module. When a user (e.g., system user at a computing devicecomprised in the web layer) wishes to use stored privacy keys toauthenticate identity in a sign in module, a user enters a first userinput (e.g., a privacy code) and a second user input (e.g., a biometricscan, a third data). A method for authenticating identity using privacykeys is illustrated in FIG. 35.

Privacy keys based on third data 3590 are generated in the same manneras described above and as illustrated in FIGS. 31 and 32. The resultingprivacy keys 3590 are transmitted to one or more servers comprised inthe administrative layer of the system. Using information comprised inone or more of a privacy key, a privacy code, a second privacy code, andparameters associated with a first data, the one or more servers locatesand retrieves the stored privacy keys 3591 from the one or more nodesassociated with the one or more servers. In some embodiments, retrievalis based at least partially on a receiver identifier and/or privacy codeidentifier.

Each of the privacy keys based on third data 3590 (e.g., privacy keysreceived from a computing device during the sign in module) is used togenerate a fourth data in the same manner illustrated in FIG. 33.According to some embodiments, a fourth data may be sign in data 3592.Each of the stored privacy keys 3591 retrieved from one or more nodes isused to generate a fifth data 3593 in the same manner illustrated inFIG. 33. According to some embodiments, a fifth data may be enrollmentdata 3593. A fourth data (e.g., sign in data 3592) may be compared to afifth data (e.g., enrollment data 3593) to generate a result 3594.According to some embodiments, if a fourth data 3592 is the same as afifth data 3593, then the result 3594 is positive. In embodiments wherea data (e.g., a first data, a second data, a third data, a fourth data3952, a fifth data 3593) is information about any one of a biometricscan, a privacy code, a login password, etc., then identity can beconfirmed if the fourth data 3952 (e.g., data entered during sign in) isthe same as a fifth data (e.g., data entered during enrollment andstored as privacy keys). A positive result may allow a user to accessone or more protected systems.

Using Privacy Keys for Secure Data Storage

In some embodiments, privacy keys may be used for secure data storage.For example, in some embodiments, a first data may comprise a sensitivedocument. The first data may be used in the manner described above togenerate privacy keys which may then be stored. In these embodiments, itmay become necessary to edit the secure data (e.g., first data,sensitive document). Privacy keys may be retrieved in these embodiments,and a second data generated in the manner described above. The systemallows for the temporary storage of the data (e.g., first data, seconddata) at a landing zone for editing. In some embodiments, a landing zonemay be comprised in any one or more of the one or more servers, atemporary database, first computing devices, second computing devices,or application. In some embodiments, a landing zone may comprise anexternal application such as Google Docs, Microsoft Word, or otherapplication. The edited data may then be used, in the manner describedabove, to generate a new set of privacy keys which may then be storedfor later use.

It will be appreciated by those skilled in the art that other variationsof the embodiments described herein may also be practiced withoutdeparting from the scope of the invention. Other modifications aretherefore possible.

1. A method of generating and distributing keys using controlledcorruption, the method comprising: registering a first computing deviceat one or more servers; receiving, at the one or more servers, a firstprivacy code and one or more parameters associated with first data fromthe first computing device, the first privacy code being based on firstuser input at the first computing device and the first data being basedon second user input at the first computing device; generating, at theone or more servers, a chunk count and a public key, wherein the chunkcount is based on the one or more parameters associated with first data,and the public key is part of an asymmetric cryptographic key pair;transmitting the chunk count and the public key from the one or moreservers to the first computing device; receiving, at the one or moreservers, data associated with a quantity of first privacy keys and asecond privacy code from the first computing device, wherein: the firstprivacy keys are based on the first data, the chunk count, and one ormore corruptors; the second privacy code is based on the first privacycode, and the quantity of the first privacy keys is equal to the chunkcount; generating, at the one or more servers, a receiver identifier anda privacy code identifier, wherein the receiver identifier is associatedwith one or more nodes and the privacy code identifier is based on thesecond privacy code; receiving, at the one or more servers, the firstprivacy keys; and distributing the first privacy keys, the receiveridentifier, and the privacy code identifier to the one or more nodes. 2.The method of claim 1, further comprising generating, at the one or moreservers, a second data based on the first privacy keys, the generatingthe second data comprising the steps of: concatenating the privacy keysto generate a concatenated key; and removing the one or more corruptorsfrom the concatenated key to generate the second data.
 3. The method ofclaim 2, further comprising generating, at the one or more servers, aresult based on the second data.
 4. The method of claim 3, wherein oneor more of the receiver identifier and the privacy code identifier arebased on the result.
 5. The method of claim 1, further comprising:receiving, at the one or more servers, two or more privacy keys based onthird data from the first computing device; and generating sign-in data,wherein the sign-in data is based on the two or more privacy keys basedon the third data.
 6. The method of claim 5, further comprising:retrieving, based on at least one of the receiver identifier and theprivacy code identifier, the privacy keys stored at the one or morenodes; and generating enrollment data, wherein the enrollment data isbased on the privacy keys retrieved from the one or more nodes.
 7. Themethod of claim 6, further comprising: comparing the sign-in data to theenrollment data; and generating a result.
 8. The method of claim 1,further comprising generating, at the one or more servers, two or morechunk names.
 9. The method of claim 8, further comprising transmittingthe two or more chunk names from the one or more servers to the firstcomputing device.
 10. The method of claim 9, wherein the first privacykeys are additionally based on the two or more chunk names.
 11. Themethod of claim 1, wherein the one or more corruptors comprises threecorruptors.
 12. The method of claim 1, wherein at least one of thecorruptors is based on the first privacy code.
 13. The method of claim2, wherein removing the one or more corruptors to generate the seconddata comprises: removing one or more first corruptors from theconcatenated key to generate first cleaned data; removing one or moresecond corruptors from the first cleaned data to generate second cleaneddata; removing one or more third corruptors from the second cleaned datato generate a base 64 of compressed data; decoding the base of thecompressed second data to generate the compressed data; anddecompressing the compressed data to generate the second data.
 14. Themethod of claim 13, wherein one or more of the first privacy code andthe second privacy code are used to remove one or more of the firstcorruptors, second corruptors, and third corruptors.
 15. The method ofclaim 1, wherein the first data comprises a targeted communication. 16.A system comprising a server, the server comprising: a memory comprisingserver instructions; and a processing device configured for executingthe server instructions, wherein the server instructions cause theprocessing device to perform operations of: registering a firstcomputing device at one or more servers; receiving, at the one or moreservers, a first privacy code and one or more parameters associated withfirst data from the first computing device, the first privacy code beingbased on first user input at the first computing device and the firstdata being based on second user input at the first computing device;generating, at the one or more servers, a chunk count and a public key,wherein the chunk count is based on the one or more parametersassociated with first data, and the public key is part of an asymmetriccryptographic key pair; transmitting the chunk count and the public keyfrom the one or more servers to the first computing device; receiving,at the one or more servers, data associated with a quantity of firstprivacy keys and a second privacy code from the first computing device,wherein: the first privacy keys are based on the first data, the chunkcount, and one or more corruptors; the second privacy code is based onthe first privacy code, and the quantity of the first privacy keys isequal to the chunk count; generating, at the one or more servers, areceiver identifier and a privacy code identifier, wherein the receiveridentifier is associated with one or more nodes and the privacy codeidentifier is based on the second privacy code; receiving, at the one ormore servers, the first privacy keys; and distributing the first privacykeys, the receiver identifier, and the privacy code identifier to theone or more nodes.
 17. The system of claim 16, wherein the serverinstructions cause the processing device to further perform theoperation of generating, at the one or more servers, a second data basedon the first privacy keys, the generating the second data comprising thesteps of: concatenating the privacy keys to generate a concatenated key;and removing the one or more corruptors from the concatenated key togenerate the second data.
 18. The system of claim 16, wherein the serverinstructions cause the processing device to further perform theoperations of: receiving, at the one or more servers, two or moreprivacy keys based on third data from the first computing device; andgenerating sign-in data, wherein the sign-in data is based on the two ormore privacy keys based on the third data.
 19. The system of claim 18,wherein the server instructions cause the processing device to furtherperform the operations of: retrieving, based on at least one of thereceiver identifier and the privacy code identifier, the privacy keysstored at the one or more nodes; and generating enrollment data, whereinthe enrollment data is based on the privacy keys retrieved from the oneor more nodes.
 20. The system of claim 19, wherein the serverinstructions cause the processing device to further perform theoperations of: comparing the sign-in data to the enrollment data; andgenerating a result.